topic Re: Variables bug with Expression editor? in QlikView

Variables bug with Expression editor?

Tue, 17 Mar 2015 10:38:19 GMT

I defined a small number of variables based on table values in a script so that I could refer to the variable, rather than directly to the table value using an inter-record function in a chart formula. This worked fine in a small application.

However, when I scaled it up to an app with a lot more data, but similar structure, it appears to cause problems. In particular, the expression editor shows "Expression OK", but the expression produces null values. Furthermore, if you type random stuff at the end of the expression, the expression editor continues to show "Expression OK", instead of "Garbage after ')'...", as one might expect it to do.

Any suggestions?

Thanks!

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 10:48:58 GMT

I think that I need more information ....

Usually there is no problem scaling up an application in this way.

I would guess that you are using a variable within set analysis and this will allow you to continue typing at the end as the code does not know the content of the variable during compilation.

I would suggest that something has happened to your variables (they either have not been specified or corrupted in some way) - Display the variable content first. That is the first place to look.

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 11:19:39 GMT

Well, what works in the small application is:

Only({<[Tariff Name] = {$(T1)}>} [Rental per month])

So, you are right that I am using it in set analysis. I just tried typing "banana" at the end of the line and the editor doesn't pick up any problem. I guess I had assumed that the closing curly bracket would tell it where the set expression ends, since it continues to pick up and highlight kewords and field names.

The same structure does not work in the bigger version, though. The variable Ta1 has the correct value when I look at it in the Variable Overview.

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 11:25:55 GMT

I also followed your advice and checked the variable content (in the small version) and

[Name] & ' ' & $(T1)

produces just the name. My understanding is that $(variablename) should instantiate to the value of variablename. is that mistaken?

Re: Variables bug with Expression editor?

jonathandienst — Tue, 17 Mar 2015 11:51:57 GMT

Open the Variable Overview and check that the variable exists and the literal or expression contained in the variable. $() will expand the content of the variable - this will be literal content, an expanded expression or expression fragment, or the value of a globally calculated variable (one with a leading = in the definition).

HTH

Jonathan

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 11:53:13 GMT

Here is a bit of set analysis that works:

Sum({$<StatusProspect = {[Sales]}, StartYearEnd = {$(#=Only(DT_year_num))},StartMonthEnd = {$(=DT_month_name_abbreviation)}>} EstimatedSalesConverted)/1000

I think that this should help

All the best

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 11:58:33 GMT

The Variable overview shows a correct literal value for the variable (in both small and large versions).

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 12:01:18 GMT

Thanks, but I'm not sure how this applies to my example. What does the $ after Sum({ do?

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 12:03:30 GMT

The $ will enable the system to use the list bar settings.

You should also see the Set Analysis part of the help files as it is very useful

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 12:05:49 GMT

Sum({$<[Tariff Name]= {$(=T1)}>} [Rental per month])

should work for you .....

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 12:11:53 GMT

I'm afraid not! It works on the small version, but not with the larger one, as with the construction using Only().

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 12:14:43 GMT

It must be the value of T1.

I would create a small text box on each application with the content "=T1" and see if they are different.....

Are you sure that the variable exists in the larger one .... ?

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 12:31:24 GMT

Both of those work fine.

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 12:33:45 GMT

Can you cut down an example and post to the site .... ?

You probably have some confidential data (which obviously should not be posted), but can you post without?

Thanks

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 12:35:02 GMT

Just a quick thought ..... Does the Tariff that is in T1 actually exist in both applications?

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 12:58:31 GMT

Yes, I am reading it from an input table.

I can post the small app - it has made-up data. I'll see if I can figure out a way of posting a cut-down version of the larger one.

Thanks!

Re: Variables bug with Expression editor?

Roop — Tue, 17 Mar 2015 13:06:39 GMT

Thanks

Re: Variables bug with Expression editor?

Peter_Cammaert — Tue, 17 Mar 2015 13:09:53 GMT

Just nitpicking: the initial expression uses T1, but your description about the larger application talks about Ta1?

A typing error, or is it that something small has changed between reloads?

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 13:16:26 GMT

I changed the name to Ta1 in the big version in the vain hope that the

problem might be a conflict with some system variable, or something of that

kind. I didn't mention it previously to reduce confusion! I refer to T1

in the small version and Ta1 in the big version.

Re: Variables bug with Expression editor?

Tue, 17 Mar 2015 13:20:24 GMT

I should have said, the table that uses the expression with reference to the variable T1 is the one entitled "Table: by user".

Sorry for any confusion!