Hi! Just try your imaginations with that: Set Analysis Wizard for QlikView | qlikblog.at
Moreover, describe with more density your task, as it connected to different solutions. Drop here a user experience work.
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.
AltState.qvw 185.8 K