But how can we reverse this logic and define what fields should be used for calculation? Or we can ask: How we can break association model in QlikView by Set Analysis?
My situation
I got application with 20 and more selectable fields. For one of the expressions I need to make sum() using selections from 3 field. Let their names be Year, Day, Month. Of course we should have possibility for making multiply selection in every field. I probably could use this example:
Sum({$<Year = {$(=only(Year) – 1)}>}Sales
But it would show me smth if I make selection of 1 year in field Year.
I want to get smth like this:
SUM( {@<Year = , Day = , Month = >} Sales )
Where operator @ make reverse logic.
I just cant get simple expression. I can write LONG expression like this:
This sounds like a perfect use case either for the P() modifier or simply use alternate states.
In the attached example I have used alternate states, they are created from the document properties.
The data model is then separated into more then the usual 1 and $ states and you can cross reference fields between the different states.
In the example app you will see that the text object will only re-calculate when you select something in the Dim1 listbox. It's a bit crude as examples goes but I think you get the general gist behind it.
This sounds like a perfect use case either for the P() modifier or simply use alternate states.
In the attached example I have used alternate states, they are created from the document properties.
The data model is then separated into more then the usual 1 and $ states and you can cross reference fields between the different states.
In the example app you will see that the text object will only re-calculate when you select something in the Dim1 listbox. It's a bit crude as examples goes but I think you get the general gist behind it.
