topic Re: Strange behaviour of variables in App Development

Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 10:46:57 GMT

I use a script which creates variables.

Their values are set within IF-clauses.

I load the script and then they work fine in the app-view, but when I restart my browser their values are different

(The values are from different if-clause outcomes).

Why do their value change when I restart my browser?

I thought their values are bound to the last value they received, from the variable editor or the data load script.

Do I need to store all variables in tables and reload them as a workaround or is there a better solution?

Re: Strange behaviour of variables

sunny_talwar — Fri, 24 Feb 2017 10:48:44 GMT

Do you have On-Open trigger which might cause the value of the variable to change for some reason?

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 11:50:08 GMT

Not that i would know - I am basically just loading and opening the app / closing browser and opening again

Re: Strange behaviour of variables

sunny_talwar — Fri, 24 Feb 2017 11:55:54 GMT

Are you able to save a copy of the dashboard and check if there is any on-open trigger?

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 12:27:06 GMT

I don't think I have the permissions to see or set triggers.

Is there a kind of trigger preventing variables to be saved?

Re: Strange behaviour of variables

sunny_talwar — Fri, 24 Feb 2017 12:29:20 GMT

I think it might be saved to one value, but there might be a trigger which changes it's value as soon as your reopen the dashboard.

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 12:35:50 GMT

It may be trivial but I noticed that the variables also reset when I don't open the app-view in a new tab but inside the data load editor-window.

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 12:56:15 GMT

I noticed something less trivial:

scenario:

var1 = true;

var2 does not yet exist

script:

LET var1 = FALSE();

LET var2 = FALSE();

after load:

var1 = true;

var2 = false;

The important thing is, that var2 is noticed as being loaded from the script, while var1 is not

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 12:59:00 GMT

New variables can be changed as I wish and keep their values,

old variables (past days) won't change.

I am working on a server - I guess this is linked to the main problem?

Re: Strange behaviour of variables

sunny_talwar — Fri, 24 Feb 2017 13:00:00 GMT

Not sure, may be pcammaert‌ can offer his expert advice here

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 13:18:42 GMT

I think the problem is linked to script variables and custom variables.

All of my old variables are displayed as custom variables, immune to script-changes but changeable by the variable-editor.

Newly created variables are displayed as script variables, can't be changed by the variable-editor but in the skript.

I just don't know why the skript-variables that I have a long time now don't count as script-variables anymore.

If I open the app-view after loading in a new tab, those old variables are detected as script variables, otherwise as custom variables.

BUG from Qlik-Sense?

I can't explain why using the gui in different ways can show me the variables with their new script value or with their old "custom" value (they were never created as custom variables)

Re: Strange behaviour of variables

Anonymous — Fri, 24 Feb 2017 13:22:40 GMT

I will use a save and load as fields - workaround, but it would be nice to know whether this is a general or specific problem.

Re: Strange behaviour of variables

Peter_Cammaert — Fri, 24 Feb 2017 16:53:04 GMT

I'm not too familiar with variable behavior in Qlik Sense... yet

I certainly can't come up with a reason why your Sense client seems to change variable values at random (opening/closing a browser).

The behavior of script variables vs "custom" variables (those defined in the user interface) however seems to hint at similar behavior in recent versions of QlikView though. For example, we did run tests and noticed that in QV you can delete script variables that were created before in the same script run. A later script run however doesn't allow you to remove them anymore, although they're still script variables ...