topic Variable calculations lost in Source Control in QlikView

Variable calculations lost in Source Control

Fri, 13 Jan 2012 01:37:31 GMT

We have implemented source control using the TFS integration.

Unfortunately, variable values are stripped out. I guess the process treats is as "data" and therefore it is not stored.

I am a heavy user of variables to simplify set analysis expressions and reuse calculations between charts and KPI gauges, so would really like it stored in source control.

Variable calculations lost in Source Control

Sat, 14 Jan 2012 20:43:28 GMT

Have you tried to define variables in the script editor instead?

Variable calculations lost in Source Control

Sun, 15 Jan 2012 22:20:41 GMT

That nearly works. The problem is some of the set analysis expressions.

='=Sum({$ <PremiumReceivedYearNum={$(=vMaxFinancialYearNum)} >} PremiumReceived)'

becomes

=Sum({$ <PremiumReceivedYearNum={(internal error)} >} PremiumReceived)

Variable calculations lost in Source Control

Mon, 16 Jan 2012 12:46:59 GMT

A workaround could be to use

LET EXPR='=Sum({$ <PremiumReceivedYearNum={$'&'(=vMaxFinancialYearNum)} >} PremiumReceived)'

instead of

SET EXPR='=Sum({$ <PremiumReceivedYearNum={$(=vMaxFinancialYearNum)} >} PremiumReceived)'

Variable calculations lost in Source Control

Mon, 16 Jan 2012 22:04:57 GMT

Thanks, that works. It will suffice as a workaround for now.

Variable calculations lost in Source Control

ToniKautto — Thu, 19 Jan 2012 19:12:54 GMT

Variable values are considered as data and therefore not saved in the PRJ folder.

By declaring the variables in the load script they will be stored in the PRJ folder and thereby will not vanish.

It is known that in some cases variable definitions containing dollar expansions can lead to the desxribed issue. For these situations please use the workaround that was already identified above, meaning that you split the expression into two strings forcing the dollar expansion to not be expanded in the script but rather when called in application.

Re: Variable calculations lost in Source Control

Tue, 31 Jan 2012 04:52:13 GMT

My next issue is with variables that include single quotes in the expression.

A variable with the expression

=Date(AddMonths(Max(YearMonth), -12), 'MM-YYYY')

Needs to be written as

LET v12MonthsToMax ='=Date(AddMonths(Max(YearMonth), -12), ' & chr(39) & 'MM-YYYY' & chr(39) & ')';

Variable calculations lost in Source Control

kuba_michalik — Wed, 01 Feb 2012 13:34:52 GMT

You can avoid that using SET instead of LET (SET simply assigns everything after the equal sign to be the variable content, single quotes or no). However, you can't avoid dollar sign expansion using SET, so if you need both, you need to write a convoluted expression.

Variable calculations lost in Source Control

Wed, 01 Feb 2012 21:42:13 GMT

Thanks Kuba

Re: Variable calculations lost in Source Control

barryharmsen — Wed, 30 Jan 2013 21:14:17 GMT

Another option, that does not require unescaping/replacing, is storing the variables in an external file, load them into a temporary table and directly assign them using the peek function. You can find an example here: http://www.qlikfix.com/2011/09/21/storing-variables-outside-of-qlikview/

Re: Variable calculations lost in Source Control

Wed, 30 Jan 2013 21:38:32 GMT

Thanks Barry. I like that idea.

Re: Variable calculations lost in Source Control

Anonymous — Thu, 05 Jan 2017 10:10:16 GMT

There is another option you can use and that is to load the current document into itself as XML to make use of the QVW header.

Re: Variable's value in -prj folder xml

Enjoy you should be able to add Variables into source control, nice and easy