topic Calculation condition error message not displaying in QV10 in QlikView

Calculation condition error message not displaying in QV10

Tue, 26 Apr 2011 18:37:19 GMT

Hi all. I have a chart that requires a certain filter value to be chosen before any data can be displayed. I created a calculation condition to look at that field, and created an error message for "Calculation condition unfulfilled" to say please choose a value for this field. Now, when I first load the QVW, that error message is not displayed. The chart is just blank white. If I choose the value to make the data appear, and then clear it again, the error message will now appear. This didn't used to be the case in QV9. When I loaded the QVW, the error message would immediately appear. Now with QV10 it only appears after I select the value and clear it again. Any ideas? Thanks!

Calculation condition error message not displaying in QV10

vgutkovsky — Tue, 26 Apr 2011 20:37:36 GMT

What function are you using for your condition? Try using GetSelectedCount(field_name)>0, which should be quite simple. If that doesn't work, then it might be a bug, but I would be very surprised. Plus there are always other ways to check the same thing that you can try.

Regards,

Calculation condition error message not displaying in QV10

Tue, 26 Apr 2011 21:23:52 GMT

Hi Vlad. Thanks for the reply. So I've further identified the issue, and I think this may be a bug. The issue arises when I open a minimized chart that has a calculation condition. So if I save the qvw with the chart opened, the next time I open the qvw it will display the error message. If I minimize that chart, then double click on it to re-open it, it will be blank and the error doesn't display. If I save the qvw with the chart minimized, then open it after re-opening the qvw, it will be blank. Do you think this is a bug?

Calculation condition error message not displaying in QV10

vgutkovsky — Wed, 27 Apr 2011 02:26:31 GMT

Oh, I think I misunderstood you before. You're not saying that the calculation condition itself doesn't work, but rather that the error message doesn't? I've seen that before and yes, I think it's a bug (although I didn't have time to report it to support myself).

Regards,