Cyclic expression in PT?

[#1]

It seems to be possible to create a cyclic group of expressions in a PT but the icon to switch between states does not appear. Am I doing something wrong or is this a bug?

If it is a bug, what are people doing as an alternative? I know that using action buttons to show/hide objects will work but I already have a number of action buttons on my page so am reluctant to have any more.

Are there any other clever alternatives?

Many thanks.

[martin59]

Unfortunately, I don't think you can change your expression if you pivot a dimension columns.

But you have to create a text object with actions (like a button, but more discrete) and put it in the caption's object.

[johnw]

I'm seeing the expression group icon fine in 9 SR5, though maybe I'm misunderstanding the exact situation. As another possible solution, you can handle it with a dimension group instead of an expression group, then detect the field name to do the appropriate calculation. See attached for both real and fake expression groups.

[#4]

Hi John,

here's the problem:

This PT has a cyclic group of expressions but the icon to switch between state does not appear. The results from the first expression in the group are always displayed. Because the expression label is not displayed when pivoting like this, it kind of makes sense that the cyclic icon will not appear as well - where would it go? Perhaps this isn't a bug but it still needs addressing by QlikTech because functionality is lost.

I like your idea of the "fake" expression group - I will definitely use that in some of my apps. Also, as Martin states, it is possible to achieve what I need using text objects and buttons.

It is quite frustrating sometimes how these sort of workarounds are necessary even when dealing with what should be a simple situation.

Many thanks for the assistance.

[johnw]

Ah! OK, now that makes total sense, and I'm not sure why I didn't understand the problem earlier. I do think QlikView should find SOME place to put the icon and expression names, but I can see how a QlikTech programmer could have missed it. I agree that it needs to be addressed by QlikTech, and I'd personally call it a bug, but even if they call it a WAD, it still needs to be addressed.