sections in the article
Question
Is there information available on what system characters are not accepted when using the String and LocaleString fields when importing data using the API?
Answer
These system characters are not accepted:
[ASCII: 0] [NULL]
[ASCII: 1] [Start of Heading]
[ASCII: 2] [Start of Text]
[ASCII: 3] [End of Text]
[ASCII: 4] [End of Transmission]
[ASCII: 5] [Enquiry]
[ASCII: 6] [Acknowledge]
[ASCII: 7] [Bell]
[ASCII: 8] [Backspace]
[ASCII: 9] [Horizontal Tabulation]
[ASCII: 11] [Vertical Tabulation]
[ASCII: 12] [Form Feed]
[ASCII: 14] [Shift Out]
[ASCII: 15] [Shift In]
[ASCII: 16] [Data Link Escape]
[ASCII: 17] [Device Control One]
[ASCII: 18] [Device Control Two]
[ASCII: 19] [Device Control Three]
[ASCII: 20] [Device Control Four]
[ASCII: 21] [Negative Acknowledge]
[ASCII: 22] [Synchronous Idle]
[ASCII: 23] [End of Transmission Block]
[ASCII: 24] [Cancel]
[ASCII: 25] [End of Medium]
[ASCII: 26] [Substitute]
[ASCII: 27] [Escape]
[ASCII: 28] [File Separator]
[ASCII: 29] [Group Separator]
[ASCII: 30] [Record Separator]
[ASCII: 31] [Unit Separator]
Comments
2 comments
Is it possible to allow these values in the fields or is it hardcoded in iPMC to disallow usage of these?
We currently do have some horizontal tabulation chars in fields, which should not have been possible according to this. This in turn causes issues when updating entities. The customer states they are required for markup-related reasons in their output systems.
Hi Willem!
At the moment, it's not allowed for these values to be inserted iPMC.
If your customer is having issues, and somehow the values were inserted into the fields, then I suggest you submit a ticket to inRiver support.
Please sign in to leave a comment.