Discussion board where members can learn more about Qlik Sense App Development and Usage.
Is there support for Alternate States and Comparative Analysis in Qlik Sense?
This email and any attachments to it are intended solely for the use of the individual(s) to whom it is addressed. It contains information which is private and may be proprietary. Any views or opinions expressed in this email are solely those of the Sender and do not necessarily represent those of Cooper Software Ltd. If you are not the intended recipient of this email, you are hereby notified that you must not use, reproduce, distribute or store it, and the message as well as its contents should be destroyed immediately. Please contact the sender if you believe you have received this email in error. Your co-operation is very much appreciated.
P Please consider the environment before printing this email.
To add Bodil's response; The plan is to introduce alternate state and support comparative use cases in more natural way. In QlikView, the use of alternate state is more focused on developers, where the developer needs to setup the use case for the users. With Sense, we would like to leverage the alternate state capability of the engine, and create capabilities for the business users. For example a business user would be able to create a new state on the fly for the current selections and assign it to a visualization to compare and explore. We will introduce alternate state to support these type of new capabilities as well as to support the use cases for the developers.
Thanks a lot!
I asked this question to Qlik in a chat during the "Visualize Your World" Virtual Forum event, and got the following useful response:
"Alternate states are not yet implemented, though there are plans for it to be there and the capability is in the current engine. There is a desire to make it a more natural experience for the majority of users as at present it can make a bit of a mess out of an application. As I understand it there are two approaches.
1) The first is to implement a duplicated data model. This is not ideal.
2) Alternatively, you might be able to achieve some of your aims using set analysis to control the impact of dimension selections on a control visualization. Basically, make a chart ignore any selections in a certain field."
Second approach in Qlik Sense, with the focus on touch first and self service discovery, is not such a great choice for this area. So it might work to create a data-island with only 1 "shadow" field, and use that selection in a set-analysis to overrule the real field. Cause I want to select for instance Brand=A on one hand, and compare with Brand=B&C.
There are indeed alternate states capabilities in Qlik Sense 1.1+ APIs, so I created two simple extensions to facilitate the use of alternate states in Qlik Sense while we are waiting for a release with alternate states support OOTB. You can check them on Qlik Branch: