If you install locally, check out the Installing and Getting Started sections in the help Installing
If you want to just kick the tires you can play with the demo site https://easyqlik.com/qsda/demo. Feel free to launch a new analysis or delete old analysis on the demo site. (The demo site is shared by anyone logged in so you may see changes other make as you play).
Though I have a more general question. We make use of variables to execute expressions (expression sheet in Excel). This way we can easily maintain them.
The thing is, is that the Doc Analyzer doesn’t pick this up. Resulting in a lot of ‘fields unused’ and makes it hard to throw away stuff. Is it possible to scan through the variables and pick them up?
I know this can become hard, even more with nested variable expressions. But what is your general idea about this?
The general idea is that a field used in a variable should be marked as in-use, even with nested variables. It works that way in my simple testing. Can you post an example I can work from?
I was short on time, but I have indeed tested it and it’s working when the calculation is created in the script.
Though when the application makes use of variable inputs say:
let vType = Total ; // But also can be Daily and it used in Variable Input in Qlik.
Sum( Sales_$(vType) ) // Used in the frond-end
The application is not able to see these combinations. Which makes sense, but this was the question that I had in the beginning. Do you think these is a possible solution for this?
