How to resolve loading CSV data when SN automatically creates column with non-standard ASCII characters?

[Todd O]

I'm loading data into SN tables by way of importing through data sources and import sets. I have plain csv files and I'm certain there are NO non-ASCII characters. However, when I create the data source and pick my csv file to auto map fiels for the transformation map, SN proceeds to create columns with non-ASCII characters as part of the name. See the image below. Why would SN have this behavior? It's messing up some other scripting I want to do where I want to match up the exact name from the CSV file. Thanks in advance.

Todd

[bernyalvarado]

Hi Todd,

I have seen that before and I believe it was a very easy fix.

Have you checked if there's a tab or some other special visible or non-visible character in your source file for that specific record?

You may want to check that using your text editor of preference and enabling the option to view special hidden characters.

Thanks,

Berny

[bernyalvarado]

Time back I believe that also happened to me while using spanish accent or special characters. I then dumped those and used normal/plain english acceptable characters .

ServiceNow handles internationalization very well, but it's a different thing to try to name it's system object fields with special characters.  

Thanks,

Berny

[bernyalvarado]

I hope this helps!

[GoBucks]

Todd, I'm experiencing the same issue while manually importing a CSV file. I'm getting that exact same non-ASCII character so my first column name is odd just like in the picture you provided showing your 'equipid' column. I've opened up Notepad++ and showed all characters. I don't see any odd characters.

Did you find a solution?