Back

Unicode Text File Source Using UTF-8 Encoding

Published: Mar 23, 2018
Post Author Written by Ethan Sorenson

SmartConnect by default has two character sets available, OEM, and ANSI. Neither of these include the special characters used in non-English languages such as ñ, á, ü. The work around is to edit the SmartConnect SchemaHeader table to inform the ODBC driver to use the UTF-8 character set.

1. Create and save a map like normal, selecting ANSI as the Character Set when creating the schema file
2
3

2. Edit the SmartConnect SchemaHeader table to use Character set ‘65001’

4
UPDATE [SmartConnect].[dbo].[SchemaHeader]
Set CharacterSet = ‘65001’
WHERE SchemaHeaderId = ‘UTF8_TEXT_TT_SAMPLE__spanishText_csv’

3. Reopen the map and preview the data source
6

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.