![]() I've attached a simple QVF file and screenshot that shows where these issues occur.įor pretty much all of our needs, switching the existing single quotes for double quotes works, but I'd like to be able to implement set analysis for Dual() values in the same way that we do for all other data types. ![]() Can someone else please confirm that they are also experiencing the issue I describe below in Qlik versions starting with November 2017? I'm not sure how to send this to Qlik as a potential bug so posting here first.ġ.) You can no longer use single quotes in set analysis to filter for field values that are stored as Dual() values.Ģ.) Since you can't filter Dual() text values using single quotes there would be no way to distinguish between these two values in set analysis without knowing/referencing their individual number values - Dual('value', 1) and Dual('VALUE', 2). ![]() This is wonderful, but I seem to have found an issue with how it was implemented. Compare price, features, and reviews of the software side-by-side to make the best choice for your business. I know that Qlik somewhat recently fixed the single versus double quote issue in set analysis so that single quotes reference literal strings while double quotes not act as a case insensitive search.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |