- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2021 07:10 AM
Hi everyone,
I'm trying to import some data from a JSON file. I configured a data source and added a JSON file attachment. Everything seems to work fine, except that special characters (such as Ä and Ø) are not properly imported. Instead, it turns it into these unicode symbols:
The issue already occurs before running any transforms.
I have already tried the following things:
- Setting the field in the import table to be a String (Full UTF-8) field (doesn't make a difference)
- Set properties field of the data source to charset=UTF-8 (doesn't work for JSON imports, only CSV)
Is there any way to properly load special characters from a JSON file import?
Since the data file is coming from an external source, using a different filetype isn't really possible and they also don't have any API technology in place whatsoever, so we're pretty much forced to stick with the JSON file import.
Any help would be appreciated, thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2021 08:05 AM
Turned out that my source file was indeed not properly UTF-8 encoded. I downloaded the file, re-saved it with UTF-8 encoding and this time it imported everything perfectly.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2021 07:31 AM
Hi,
It may be that the chatset properties must be configured from the source, however it is possible to do a post-treatment using decodeURIComponent:
var yourJSON = "F?B?DBERGET";
var formattedText = decodeURIComponent(yourJSON);
gs.info(formattedText);
MVP 2025 ✨

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2021 07:39 AM
Put the text into a charset encoding tool such as the one at Webatic to confirm that your data is really UTF-8 instead of another charset such as ISO-8859-1 or windows-1252.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2021 08:05 AM
Turned out that my source file was indeed not properly UTF-8 encoded. I downloaded the file, re-saved it with UTF-8 encoding and this time it imported everything perfectly.
Thanks!