- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik sense September Release adds Unqualify
Hi all,
I installed the qlik sense september release (desktop), and found that next my existing sections, with non-automatic generated scripting, an automated section is added with
Unqualify *;
When loading data, this results in an error on some dashboards (not all):
Unexpected token: 'Unqualify', expected one of: '(', 'Where', 'While', 'Group'
I've been able to work around the error by dragging the auto-generated section to the top of the section list. But am curious as to why this is added.
BTW: when searching for qualify in all sections, there is one unqualify statement in the datamanagertables part. there are no qualify statements.
- Tags:
- unqualify
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It sounds like you are not terminating your last script statement with a semicolon. The added "Unqualify *;" should have no impact on your script as the last statement -- if you have terminated the previous statements.
-Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jacob-Jan,
I am experiencing the same issue. Even when I remove that section and reload the data, it appears again. I expect this is a bug and I have submitted a case with Qlik Support about it. Will update here when I hear back!
Cheers,
Stijn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It sounds like you are not terminating your last script statement with a semicolon. The added "Unqualify *;" should have no impact on your script as the last statement -- if you have terminated the previous statements.
-Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I got a reply from ! Qlik Support:
"Thank you for filing the support ticket. For your information, the reported behavior is a known issue in Qlik Sense September 2018, which has been investigated in bug QLIK-89813. The bug is now fixed and the fix will be delivered in the coming Qlik Sense November 2018."