Convert to Legacy Error Cluster VI Does Not Decode JSON Special Characters

Issue Details

• In my LabVIEW VI, I have a JSON encoded error cluster that consists of special characters. When I convert this back to the standard LabVIEW cluster, the special characters are not converted. Is this expected behaviour?
• When I use Convert to Legacy Error Cluster VI to convert a JSON encoded error, special characters such as \n or \\ remain in the JSON format. How do I avoid this?

Solution

This is intended behaviour for the Convert to Legacy Error Cluster VI.

Special characters appended by the JSON encoded error are not omitted/converted to accommodate for cases such as:

• These special characters were entered as literals.
• Users that wish to keep track of formatting rules, so that this information can be parsed elsewhere.

If your error includes JSON encoded special characters that you wish to convert to tabs, end of line characters etc. then it is necessary to parse the string yourself.

Attached is an example VI that demonstrates how to use the Match Regular Expression and Unflatten From JSON functions to implement this conversion.