topic Re: Variable's value gone with -prj Folder in QlikView

Variable's value gone with -prj Folder

senior_freshmen — Sat, 16 Nov 2024 20:44:21 GMT

Hello,

i got problems with implementing Version Control for QlikView.

We offer different language tables for our Dashboard. These languages and the Labales are stored in a Excel File(See my attachements).

To display the Name for the current selected language, we use the formula:

=only({1<Label={'Bezeichnung'}>}$(=Sprache))

Now when I create the PRJ Folder, all my descriptions are gone.

Error message after Reloading the DashboardLayout of the Object with the Formula-Descriptionlanguage Table

How can I solve this problem?

Sincerely

Re: Variable's value gone with -prj Folder

senior_freshmen — Tue, 04 Jun 2019 06:19:35 GMT

Anyone?
To specify this problem:
With creating the prj-Folder these problems only occur in my collection Box. In this Box, each description which is more than blanc text is deleted. So not only the variable values are gone, the variables itself are deleted from description(= title bar) and i dont know how to workaround this problem.

Can anybody suggests something?

Sincerely

Re: Variable's value gone with -prj Folder

marcus_sommer — Tue, 04 Jun 2019 06:43:48 GMT

It happens only within the container and the variable itself (if you look within the variable-editor) and your translation-table are available within the application or are they completely gone?

- Marcus

Re: Variable's value gone with -prj Folder

jerrysvensson — Tue, 04 Jun 2019 07:03:34 GMT

Quick question.
Variables created in app are not stored in prj.
You have to create all your variables in the script.

Re: Variable's value gone with -prj Folder

senior_freshmen — Tue, 04 Jun 2019 07:53:08 GMT

Thanks for your answer,

yes this only happens in the Container.All other transalations formulas in the Dashboard are active.

I know that variable values are gone at Versioning so I load all my Variable-value pairs in the script. That works so far what means that they are accessible in the Variable-List of the Document.

The Problem is the container. It deletes not only the value, but also the variable declaration itself.

So in the title bar, my description "=$(=var_Bericht)" switches to "-" and I dont know how to deal with that.

Re: Variable's value gone with -prj Folder

jerrysvensson — Tue, 04 Jun 2019 07:54:25 GMT

Could be a bug.

Re: Variable's value gone with -prj Folder

marcus_sommer — Tue, 04 Jun 2019 09:26:50 GMT

Just try if another expression within the container-objects-titles remain, maybe some dummy like:

= 'test ' & num(sum(AnyValue), '#.##0')

If this worked you might consider to change your logic from variable-values to field-values, for example by loading your translation-table with a crosstable-statement and using then an expression like:

=only({1<Label={'Bezeichnung'}, Sprache = p(FeldSprachAuswahl)>} BezeichnungsFeld)

- Marcus

Re: Variable's value gone with -prj Folder

senior_freshmen — Tue, 04 Jun 2019 10:54:32 GMT

Unfortunately it remains the same with a dummy. All logical comparisons seems to be not suitable.

Re: Variable's value gone with -prj Folder

jerrysvensson — Wed, 05 Jun 2019 10:44:17 GMT

If possible have a look in the xml files in prj folder.
You should be able to find the label expression there.

Re: Variable's value gone with -prj Folder

Brett_Bleess — Mon, 08 Jul 2019 19:17:06 GMT

Hey guys, I may have found an answer for you on this one in the following bug:

Variables used as name labels in Container Objects disappear after the application is saved when using the PRJ folder

The ID is QV-13206, and R&D stated the following as to why it would not be addressed:

Variables are classed as Data

PRJ Files do (may not) save Data

If a variable is necessary for a QVW to work then its value should be set in the Script as a SET or a LET. Once the QVW is recreated from the PRJ folder and is reloaded, it will work again.

This is best practice for PRJ folder usage. Saving variable values in PRJ files has never been how it has worked.

Hopefully this fits and tells you what you needed to know and you can maybe figure out how to set things in the script and call that in the label etc.

Regards,
Brett