I receive Japanese Characters from customer and Boomi is not parsing the file for the correct length of the file. How do I fix this issue. I tried Decode to UTF-8 but still I have minor issues.
The best way is to go back to the source system and ask them for the changes to be made.
The challenge is that default encoding can be changed at atom level and it will be dedicated to that atom hence again changing is a bit tedious one again.
But still you can handle in the process development it needs some focused time.
Thanks Srini !. Unfortunately we are SIT cycle testing and we cannot go back to customer at this time due to Business reasons.What is alternative to fix this issue. Appreciate your response asap.
Thanks for your tips
You need to find out from the customer what character set encoding the inbound documents are using. Then (assuming that you are running an atom with the UTF-8 character set as default), you need to insert a character decode step in your process which converts from the customer's chosen character set to the atom default (presumably UTF-8).
Thanks James !. Already did it but for some reason the Groovy code does not parse the Japanese characters correctly , causing issues in the output of the map.
Any other suggestions.
How do I determine the Character Encoding of the Input file ?.
Default encoding of my Atom is UTF-8
It is configured to UTF-8
The groovy script splits the single record to multiple files with Individual record types.
Sorry Unable to attache the file
As James said above, the best way to determine the file encoding would be to ask the producer of said file what encoding they use. Trying to determine this programmatically is pretty difficult and still not 100% reliable: How to detect the encoding of a file? - Software Engineering Stack Exchange
You will need to know the source encoding before you can use the Data Process decode step to decode FROM whatever the source encoding is to your Atom's encoding (i.e. UTF-8). In other words you need to configure this shape with the source encoding, not the destination (UTF-8).
You can't attach files to thread replies so just paste your script in the body.
Thanks Adam !. That points to right direction.
Retrieving data ...