Load treating Variable in Wildmatch with double ''
Hello, i recently have started using Qilk and am trying to the a hang of it.
I am facing an issue with Wildmatch when I run the load commmand.
I have an list of company names .csv which I am trying to match against names in qvd.
I create a variable which wraps all of entries in .csv resulting in: '*name*',
after which i use it when i load the db data in if statement , IF(WILDMATCH(UPPER( Db_name), $(list)),Db_name, 'n/a')
when i run the debug it works fine, when i try to load it automatically wraps everything in double quotes like ''*name*'', thus failing the query, any better ideas how to tackle this. PS yes i only have names to work of so am unable to create any joins
There are different ways to create the list + assigning the result to a variable + calling the variable again - and all parts must be suitable to each other because the content-type and the specific context will have an impact if the final result is valide or not - and the above of isn't:
Concat('*''' & pattern & '*''' ,',' )
Sounds more complex as it is - ideally the above isn't developed within the origin logic else as a dummy (maybe within a separate app) within an inline-load and then showing the field(s) in a table-box. Quickly are n attempts done to move/add commas, wildcards, quotes and so on - until it looked as if it has been manually written.
Like hinted in the above suggestion I tend to create an incomplete list and adding the missing start/end of a valid list within the call of the variable - which minimized the extra efforts to add them to the field-content or around the aggregation and/or counting-methods within any loop-approaches.
The only aspect in which I experienced an auto-quoting to existing quotes is when the data are loaded as txt from a csv or from_field and within the file-format statement is any msq activated. If this is your scenario you may try to replace it with 'no quotes'.
You may also consider a different way which may be a mapping like:
m: mapping load Field, '< Match >' from X;
t: load *, if(wildmatch(Check, '< Match >'), Field, 'n/a') as Field_N; load *, mapsubstring('m', Field) as Check from Y;
IMO the quoting-interpretation creates more challenges as it solved. If an unique field-delimiter exists it should be disabled - and if not the load of the data needs a more or less expensive special treatment (it's not specifically related to Qlik else nearly all tools struggle with it by using (old) standard-libraries from Windows).
