Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

NULL as a result: problem with the length of the expression

Hello All,

I'm facing following issue:

I have an expression that gives me NULL as a result. It is built by the sums/multiplications of many statements.

I checked all parts and they worked just fine. So I started to comment one statement by one to figure out what might be wrong. I was shocked when I found out that QlikView (8.5.6299) gives NULL result if the length of expression is too big. Can it be even possible?

Have you ever noticed something similiar?

Thanks in advance for your help.

Kind regards,

JTPro

1 Solution

Accepted Solutions
Not applicable
Author

Hello All,

I have received an answer from QlikTech:

"There was a limit on how long expressions could be when being expanded from variables and the limit was around 1000 characters.
I know that this has been fixed for QlikView 9.00.7257 and it works fine when I'm testing the document in this version.
This will probably be ok in the next Service Release for 8.50 which is due out at the end of October..."

I think it is about time to move to version 9 🙂

Kind regards,

JTPro

View solution in original post

10 Replies
markmccoid
Partner - Creator II
Partner - Creator II

Hi,

I just tested this in v9 and put in 1944 COUNT() statements without an issue. How long is the expression?

Could it be when they are combined an error in the logic happens?

Could you post the expression?

Mark

Not applicable
Author

I just whipped something up in QlikView 8.50.6261.5. I think there are over 2,800 Sum statements in the expression (34,000 characters) and it it calculating correctly.

I also heard in another thread, someone was using actual expressions with over 5,000 characters and having no problems (other than trying to fit an expression that long in QlikView's small expression boxes).

biester
Specialist
Specialist

@jtpro,

please post your exact expression ! Why should we guess?

Rgds,
Joachim

Anonymous
Not applicable
Author

It's unlikley that the problem has anything to do with the expression length. One of my apps has expressions that take a dozen pages when copied to MS Word. Ick!
It is probably something in logic. No way to guess without seeing it.

Oleg_Troyansky
Partner Ambassador/MVP
Partner Ambassador/MVP

Not applicable
Author

Hello All,

Thank you very much for your help.

I could not reproduce my problem in the simple application.

Let me first ask QlikTech support for help.

If I found out what was wrong with my expression I will come back to this post.

Kind regards,

JTPro

Anonymous
Not applicable
Author

@Oleg,
Yeah, simplicity... A very Devil specific "what if", and it was before QlikTech came up with the input fields. Clients sometimes get over-excited about QV, and start to think that it can do anything.
(And it usually can Big Smile)

Not applicable
Author

Hi All,

QlikTech support is not responding, so I have decided to write about my observations.

I have noticed, that there is a problem with the variable evaluation.

My original expression is put into the variable and it looks like that:

(
$(vPROG_B_MNaT_DM)*$(vPROG_B_T_DM) +
$(vPROG_B_MNaT_DF)*$(vPROG_B_T_DF) +
$(vPROG_B_MNaT_DP)*$(vPROG_B_T_DP) +
$(vPROG_B_MNaT_HM)*$(vPROG_B_T_HM) +
$(vPROG_B_MNaT_HP)*$(vPROG_B_T_HP) +
$(vPROG_B_MNaT_HF)*$(vPROG_B_T_HF)
)
/($(vPROG_T))

The problem is that QlikView does not evaluate all variable. So, as a result (in chart) I have:

Normal 0 21 false false false PL X-NONE X-NONE MicrosoftInternetExplorer4

=(

(SUM({$<[GB: W] = {"ABC"}>} IF ([KT: B] <

….

BUDZET] < '$(vPROG_ReloadWeekPeriod)',,)) +

$(vPROG_B_MNaT_HP)*$(vPROG_B_T_HP) +

$(vPROG_B_MNaT_HF)*$(vPROG_B_T_HF)

)

/($(vPROG_B_T))

Not all variables have been replaces by the appropriate expresions. It looks like QlikView has a limitation on the variable evaluation?

Kind regards,
JTPro

Not applicable
Author

Hello All,

I have received an answer from QlikTech:

"There was a limit on how long expressions could be when being expanded from variables and the limit was around 1000 characters.
I know that this has been fixed for QlikView 9.00.7257 and it works fine when I'm testing the document in this version.
This will probably be ok in the next Service Release for 8.50 which is due out at the end of October..."

I think it is about time to move to version 9 🙂

Kind regards,

JTPro