Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsThis behavior was reproduced by Qlik Product Support and a new bug was logged to request R&D to investigate the behavior. QLIK-93710
This bug was closed by R&D as working as designed. The fields can be concatenated by a similar expression in the load script and a sort by added to set the sort order in the load script to use that new column. But there are still issues with the sorting of that string based on the second part of the concatenated field.
Adding the sort by in the load script changes if ascending or descending works properly with respect to the 2nd part of the column which contains the two other fields concatenated together. Without the sort by statement in load script: descending works properly and ascending does not. With the sort by in the load script, ascending works properly and descending does not.
There were only two ways found to fully workaround the behavior:
1. Perform the concatenation outside of Qlik.
2. Sort the data outside of Qlik prior to the data load and add a new column with sequentially increasing values to sort by in the load script.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us