Hi Luke. as requested. here is an issue we are facing and ideally looking for a fix to the package.

we currently utilise alternate states within qlik sense, and mostly utilised within the the expressions/application. this is handled by allowing only certain states to make changes to charts. for example.

so if i create an alternate state in qlik sense app - lets say this is called 'state_new' i then need to be able to call and use this within the motor filter and also the charts being rendered / KPIs being built.

lets say - i have a bar chart that is currently rendered with and expression e.g

sum({$<DIM1=p({state_new})>}MY_SPEND)

this means only this object would be updated if the motor filter / selection was using the alternate state. these then wouldn't show in current selections which would also be useful as they are flags (switches) that are toggled on and off

so if there was a feature in motor filter / switches, that allowed a state name to be called, then the engine to allow for this state to be called it may work the same as sense.