A user loads a .txt file into Qlik Sense that comes from another data source. Let's say, the first line has a Line Feed (LF) in the m...
A user loads a .txt file into Qlik Sense that comes from another data source. Let's say, the first line has a Line Feed (LF) in the middle which breaks it in 2 lines, and there is CR LF at the end of the first and the second lines. And the user wants to prevent the LF (when it comes without CR) from breaking the line when loading data by treating it as another alpha-numeric letter.
Since this is more related to a data modelling issue, rather than to a problem with the product, please, consult the data sources owner, to check if the LF in the data point is correct and if the data values can be quoted at export.
Probably, this file is the result of a system that doesn't apply quotes correctly, together with an underlying data quality issue.
In this scenario, it is important to know the data format standard used by the source system (if you want to prevent the LF from breaking the line (when it comes without CR)). For example, you also need to understand if the "LF" should just be removed or whether it actually has some meaning worth preserving.
The Qlik Engine considers all line-endings to be equally valid. LF/CR-LF/CR/ (and even LF/CR) are treated the same way. The traditional way to handle embedded line-ends in the Engine is to use quoting, which returns the expected result.
The data format of this file does not logically define how it should be interpreted. A line break can not represent both a new record and character. To clearly define that something is part of a data point, it can be quoted.
Please, refer to the "Quotes" and to the "Select data in the data load editor" articles for more information about quoting in Qlik Sense.
If we work with this unusual format when "CR-LF" is considered as a new line, while a lonely "LF" is considered to be just another alpha-numeric letter, it is not supported directly by the Engine.
Internal Investigation ID: