Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
evan_kurowski
Specialist
Specialist

What expressions can be used in Document Properties / Using a variable as another variable's input constraint list

Situational_usage_of_variables.pngHello Qlik Community,

I've seen prior discussions regarding usage of a variable in the Document Properties & as an Input constraint for a second variable.

What is confusing to me is that these entries still have the [...] ellipses button, and allow expression building.  There's plenty of inputs throughout the QlikView interface that don't offer expression building, so what types of expressions are allowed in the Document Properties: General tab? (otherwise, why have the button?)

For the variable inputs, my issue isn't that referencing the constraint list of one variable be derived from a string formed in a second variable.  What I'm having trouble with is that a hard-code will use the semi-colon delimiter, but when that same value is placed into a variable, the delimiter scheme switches to comma.   (and lets say I wanted to use a full name field in last, first format and attempt to populate my default list, this presents additional issues)

Any thoughts, ideas Qlik Community?  You assistance is much appreciated.

2 Replies
petter
Partner - Champion III
Partner - Champion III

Yes - I encountered the same issue. Not with my own computer - but with someone I was helping on this forum. I never had a problem with hard coding or with a constraint list coming from a field or a variable. It always worked with a semi colon.

Issue #1 I can reproduce on my laptop - and I guess that this is an oversight/bug/inconsistency - there should never had been an ellipsis after the Title in Document Properties. The Title is meta data and making the title into something that varies is a bit strange anyway and would be strange also on the Access Point.

The rest of the problems are not reproducible on all setups so I guess that some language settings variations might cause it. I use a computer with Windows 7 and with Norwegian settings for number and date settings, but English as the language for all strings and texts.

evan_kurowski
Specialist
Specialist
Author

Yes thank you Petter, removing the ellipses in the Document Properties title box would probably be good.  I mean after all it is the first possible input cell in all of the Document Properties menus, therefore for newly adopting users it is likely that many of them will explore this feature first.  What is their first result if they attempt to create an expression there?  I'm guessing confusion.

Also, as a side note, I would recommend setting "Save Before Reload" as the default setting of new Qlik installations.  Could probably recount a dozen stories of new users who were frustrated because they were building their very first scripts, attempted a reload without saving beforehand, encountered a syntax error, and had their entire coding attempts wiped out.  I've seen people give up on the product right then and there, done before they ever even started.

As for the input constraint, attached is an example where I can get a field list from =CONCAT({1} [FrenchFrySize],',') but you can see my need for further adjustment if the values themselves use a comma.