Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Alternate States

Hi,

I was wondering if any one has had any performance issues using Alternate States.  I have a rather large data set and was thinking about using multiple alternate states for various visualizations.  I currently have built out 7 and haven't seen any slowness, but am going to end on 10 or 11 and wanted to see if others have run into any issues.

1 Solution

Accepted Solutions
sudeepkm
Specialist III
Specialist III

Alternate to "alternate states" could be

1. Loading that dimension field Person as a different field like PersonX (x as 1, 2, 3, .. n) in another table not linked to the main table.

2. Then building multiple versions of the same chart and multiple list boxes having Person1, Person2 .. etc respectively

3. Use expression with set analysis to use the current selection of the list boxes respective to each version of "Person" field.

This is how I did when we didn't have Alternate states. I'm not sure how it would be based on performance. you can check though.

View solution in original post

8 Replies
Clever_Anjos
Employee
Employee

Yes, you have performance implications using Alternate States.

Usually we use 2 states to make comparison between 2 sets.

Why do you need 7 ? Can´t you reuse them between comparisions?

Not applicable
Author

On a single tab, I have 7 small visualizations that all use the same fields and I do not want them interacting with each other. 

Clever_Anjos
Employee
Employee

Can´t you use Set Analysis disregarding selections?

Not applicable
Author

Perhaps? I didn't know how to do that.

How would I accomplish that?  For simplicity, let's just say I have 2 states for 2 different charts.

State 1

Chart 1: Pivot Table

Dimension: Person

Dimension: Service Date

Expression: Count Service Date with set analysis limiting what to count to a specific scenario

State 2

Chart 2: Pivot Table

Dimension: Person

Dimension: Service Date

Expression: Count Service Date with set analysis limiting what to count to a different specific scenario

If I click on a Person in Chart 1, I do not want Chart 2 to drill down to shown only that Person.  I want it to remain untouched. 

Clever_Anjos
Employee
Employee

I don´t see another solution besides Alternate into your scenario. Prepare to add RAM to your QVBox

Not applicable
Author

Darn, I was hoping there was a better solution!

sudeepkm
Specialist III
Specialist III

Alternate to "alternate states" could be

1. Loading that dimension field Person as a different field like PersonX (x as 1, 2, 3, .. n) in another table not linked to the main table.

2. Then building multiple versions of the same chart and multiple list boxes having Person1, Person2 .. etc respectively

3. Use expression with set analysis to use the current selection of the list boxes respective to each version of "Person" field.

This is how I did when we didn't have Alternate states. I'm not sure how it would be based on performance. you can check though.

Clever_Anjos
Employee
Employee

RAM is not that expensive nowadays