Qlik Sense using alternate states within set analysis

[hopkinsc]

Hi all,

I am migrating a QlikView document over to Qlik Sense. The QlikView version uses an alternate state called  [WOW] and i have an expression that uses the following syntax..

sum({<PerformanceWeekCommencing=,ShowName=,PerformanceMaturity=,TransactionDate = [WOW]::TransactionDate>} SoldValue)

I can't get the same expression to work in Qlik Sense. The expression still considers the selected or possible values in the default state TransactionDate field. 

Does anyone know if I am doing anything wrong please?

Thanks in advance

[Digvijay_Singh]

Not sure but if you are migrating As-Is then you would need to create alternate state in Qlik Sense as well. Is that a Filter showing Transaction Date in a qlikview app?

[NadiaB]

Hi @Digvijay_Singh 

Our documentation to male reference to an specific field is found here 

Implicit Field Value Definitions

https://help.qlik.com/en-US/qlikview/May2022/Subsystems/Client/Content/QV_QlikView/Examples%20of%20A...

Kind Regards.

[hopkinsc]

Thanks for the replies

@Digvijay_Singh 

Yes, i have created the alternate state in Qlik Sense. 

In the QlikView app, there are 2 list boxes for TransactionDate. one of them is in the default state and the other is in the new alternate state (WOW). 

I have 2 expressions, 

sum({<PerformanceWeekCommencing=,ShowName=,PerformanceMaturity=>} SoldValue)

This sums SoldValue while ignoring the 3 listed fields, so this would take into account any selection on the Default state TransactionDate listbox.

sum({<PerformanceWeekCommencing=,ShowName=,PerformanceMaturity=,TransactionDate = [WOW]::TransactionDate>} SoldValue)

This does the same as the first expression but it also includes any transaction date from the WOW state TransactionDate list box.

This works in QlikView but Qlik Sense returns the same result for both expressions, and its the first expression result that the second expression is returning, so it's ignoring the WOW state. 

@NadiaB 

The link provided is for QlikView, this works as expected in QlikView, it's Qlik Sense that the behaviour differs. Are you able to help with a Qlik Sense solution please? 

[NadiaB]

Hi @Digvijay_Singh 

 I did a quick test with demo data (Ctrl + 0 + 0)  and the same syntax for QV worked in QS, 

My bad, the documentation for QS is here: https://help.qlik.com/en-US/sense/May2022/Subsystems/Hub/Content/Sense_Hub/Visualizations/alternate-...

Could it be possible to try with demo data? something basic and verify it works? Just to rule out that something might be wrong with data format/data model, etc in the new app?

Hope it helps. 

[hopkinsc]

Thanks @NadiaB , I've already seen this help page, unfortunately, the examples are not really real world examples, they are the simplest form. 

I will try and get some sample data together and attached it here, but if your example worked then it could be the data model. 

Are you able to attach your example by any chance?