Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
NathalieLuna
Contributor II
Contributor II

INCLUDE-statement file formatting errors

Hi guys!

I have previously used the Include-statement to include centrally controlled script-snippets, e.g. variables or locale-info or even full load scripts without issues. 

So far, the files have been in English only. But now, they also contain some special characters from Swedish, e.g. å, ä, ö. The txt-file I am trying to include is saved in UTF-8 format and renders well outside of Qlik Sense. But when running the script now I get errors due to the fact that the data field eg. is called "År" and Qlik is trying to (via the txt file script) pull "Ã...r".  

NathalieLuna_0-1596787508202.png

Same result nomatter if I use Include or Must_Include. 

Is there any way of telling Qlik that it is looking at UTF-8 formatting or is there some other fix for this? 

Labels (2)
1 Solution

Accepted Solutions
2 Replies
NathalieLuna
Contributor II
Contributor II
Author

Thank you, yes it did!

The BOM-header requirement is a bit of a special thing 🙂  

In case that post is deleted due to old age, I'm adding a pic of his solution here: 

NathalieLuna_0-1596789756754.png