Any possible solutions for apps on a Qlik Sense 3.0 server losing variable definitions loaded from an external file after being copied or published?

[#1]

We are loading a list of variables with expressions from an Excel file (in an approach similar to this one) into our Qlik Sense 3.0 app on our Qlik Sense server and this works well during development in a personal stream.  However, when someone else on our team copies the app from one person's stream to another, the variable definitions are lost, requiring a reload.  That is still not terrible (only a short amount of time is needed to reload the data before someone can continue working), but we are finding that the variable-dropping issue also occurs when we publish an app that has variables loaded in this way to the Everyone stream and, to my knowledge, there is no way to reload the data at that point. 

Has anyone else encountered this and, if so, has anyone found a solution?  We would really like to find a solution because we have found it helpful to manage our growing list of variables in an external file.

For reference, we have also attempted to move the variable definitions directly into the data load script with a SET statement for each variable, but this approach is not reproducing what we got with the load from the Excel file. 

[lironbaram]

hi

don't know about you loosing your variable definitions

but of course you can reload a publish app

so you can schedule a reload of the app in the stream

[#3]

Thank you, Liron, I don't have much experience with the QMC, so we will have to see if scheduled reloads offer us a workaround.  If anyone has any suggestions regarding the variable definitions getting lost, that would still be greatly appreciated!

[#4]

Thanks again, Liron.  I just tested a manual reload by running a task in the QMC and that, unfortunately, did not populate our variable definitions.  Any other suggestions would be welcome!

[#5]

Here is what seems to have solved this issue for us:

1. Manually deleting all existing variable definitions we had in the app from previous work (before changing our approach to instead load the variables from an Excel file) that were created from the variables overview on the bottom left corner of the screen.  For reference, many of the variable names we were loading from the Excel file were the same as variables we had manually created some time ago in the app itself, although the expressions for the variables were different. 
2. Re-running the data load script with the loop to load variables from an Excel file.
3. Publishing our app.

After that, our app was working as expected.

[Lee_Matthews]

It is very difficult to point to any one cause here, as there are many different scenarios described. The most important point here is that you must raise a support ticket when such problems occur, as then support can obtain any site / app specific information and can manage the issue towards a resolution.

- In terms of the original thread, I believe version 3.0.0 used the older synchronisation architecture, where apps were synched between multiple nodes in the site. It is possible a bug caused changes to be overwritten when the app was synched incorrectly. However 3.0.0 is so old it is not worth delving into this deeper as I expect that site has long since been upgraded.

- There is some discussion about variable definitions getting lost. This can easily happen if your load script is overwriting variables each time the app is reloaded. When assigning values in a load script please be aware of the difference between SET and LET, as these can give different results. I believe changes made to a variable value when out of edit mode are relevant to that session only, so please also be aware of that fact.

- Qlik Sense uses certain 3rd party libraries like jquery and angular. If you are using extensions those extensions could use a slightly different version of such libraries. Version conflicts might explain some unpredictable results when extensions are used to manage variables.

- Qlik Cloud is another environment altogether. Any problems with saving data there could be caused by session or web socket problems. Qlik Cloud produces extensive logs that let the admin team diagnose problems, so please raise a support ticket to help the team identify the cause and resolve it in future.