Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: Tim MeagherHey,
What version of LAL are you using?
It looks like the JSON data being parsed cannot be mapped to the character set of the output field to which it is being written.
There are two parameters which would affect this behavior: Charset and CharacterDataOutputFieldType.
In general the node tries to be smart about picking the defaults for these values (as documented in the parameters' help) - however, if you are processing data from a file, it can't always pick the most appropriate value - particularly for the Charset.
If the data you are processing is coming from a file, you may need to set the Charset parameter correctly to specify the character set of the JSON data file used.
If you can post a sample of the configured node and the data it is trying to parse, this would assist in identifying the problem.
If the data is sensitive and you can't post here or provide a "cleansed" version, then perhaps this is something you can take up with your Lavastorm Support representative.
Regards,
Tim.