Can not encode the string in the character set supported by the RDBMS

When using a flow to write data to Landmark, we keep getting this error: "Can not encode the string in the character set supported by the RDBMS"

when characters are used that Landmark seems to not like. For example, an ' in the field that is expecting a name but the name is O’Farrell - we get the error. What can I do to ensure all the fields are void of "special characters" or prepare the data that will make the DB happy when writing to it? We are using MS SQL..

Thank you.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

jreese

What node are you using to write the data to Landmark. We have names like your example and the only time we experience any issues is if we need to include them in a SQL query. Have never had an issue with the Landmark Transaction node. Only difference is we are on Oracle.

chris-mccullough

Thank you for your response. They are all landmark Trx nodes writing to the Talent Acquisition related business classes, like Candidate, Employee, etc..so, what happens in a nut shell is that a 3rd party vendor hosts the job applications....data is collected and put into an XML package that gets sent to us via REST calls.. like your name, past employers names, etc, etc..those values may contain characters that seem to make the DB unhappy, for example, a name like Piñon... the tilde breaks the writing of the name to the candidate business class and we get that error message "Can not encode the string in the character set supported by the RDBMS". I am grappling with trying to loop through all of the variables and either strip out special characters...which seems impossible OR there must be a certain encoding that needs to happen that would prepare the text for writing...like UTF-8 or something...but im trying to decipher what "Can not encode the string in the character set supported by the RDBMS" actually means.

russel-cornelson

When your Landmark Environment was installed was the database not setup for Unicode Support? I believe that is a section covered in the database setup "Pre-installation section" of the Landmark Environment Installation Guide. The error you are seeing, to me, means you are trying to insert/modify a record in the database using a character that is not supported by the database.

The way I see it you essentially have two options:

1) What you are discussing above where you try to find the offending character and strip it out.

2) There used to be a way to update your character set to unicode for the landmark database; if memory serves it was the changeda command. But for this you want to run this past your Infor Installer; I think I did this once a LONG LONG time ago when I was on the landmark environment team. But sooo much has changed since then I can not possibly give the instructions with confidence.

Copyright © 2025 Infor. All rights reserved.