UTF-8 byte order data included on first record when using file
A file listener is configured to fetch a CSV file and create a case for each record in the file.
The CSV file contains the following pattern type: Integer String, String, String.
The first case created, displays an error indicating that the integer value from the first record (only the first record) is not an integer. All other records process correctly.
When the value on the UI is replaced with another integer, the application considers it as an integer and continues processing.
When the actual value from the UI is copied and pasted to a tool where the value is converted to HEX, the UTF-8 byte order mark is included.
22 is not an integer value
Steps to Reproduce
- Create a simple Microsoft Excel file using the pattern: Integer, Sting, String, String. Do not include a header.
- Configure a file listener or service to retrieve the file and process it one record at a time.
- Configure the Service File to use UTF-8 encoding.
- Configure the Service File request to use a Delimited ParseRule.
- Configure the parse rule to map data to the Clipboard.
- Configure the Service File request to invoke an activity that creates the work item.
A third-party product issue.
Excel 365 generated CSV files were encoded using the UTF-8-BOM. This is not a supported encoding format for file listeners.
Make the following change to the operating environment:
Ensure that the files which are fetched are encoded using ASCII.
0% found this useful