A Collection of Qlik Variables
| File |
|---|
| Qlik Dollar-Sign-Expansion |
| Qlik Error Variables |
| Qlik Value Handling Variables |
| Qlik Variable Naming Conventions |
| Qlik Variables - ErrorMode |
Qlik Variables are data type agnostic! Dynamically typed. This includes expressions that we can expand
We can add variables from the Variables Overview when editing your app, or in the Load Script
When you SET a variable, this value stays constant no matter what the end-User does. Meaning selections will not change it as it is a constant value
The LET command is evaluated at runtime
You should always have a prefix for your variable names, this makes it easier to re-use and find, see Qlik Variable Naming Conventions
System variables are system-defined and info about the Qlik Sense app, these are the values that are set within the default Main script in the Script editor
Miscellaneous
If a variable is created w/in a script and then that data is loaded, that variable cannot be deleted from the app itself. Even if that variable is commented out from the script itself and re-ran, the variable will not disappear from the app itself. That variable does, however, become deletable after that point.
The # symbol can be used before a variable-name in dollar-expansion to tell Qlik, “Please represent this as a numerical value”. By design, all Qlik variables are strings, but this is a way to communicate to the application to expect a numerical value.
Variables and Subroutines
When sending a variable into a subroutine, it is not necessary to Dollar-Expand it. In-fact, this will cause a semantic error.