Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have about 10 alternate states in my application that I use for various purposes. Since I make different selections to the same field in multiple states pretty regularly, I'm wondering, when it comes to Field Event triggers which state gets checked? I've tested this a bit and get mixed results:
I have a field called data_year which exists in a state named Global. Setting an OnSelect trigger on data_year through the document properties dialogue seems to fire off as expected; when I make a selection in my data_year list box in the Global state, the trigger fires and the actions are performed.
However I have several other triggers that are set up the same way that do not work as expected. It's as if the selection for the OnSelect trigger is not being detected. This seems to happen at random. Some of the fields I've tested have selections in the default state, and some exist in other alternate states.
Can anyone shed some light on this?
Based on the tests I've run, it appears field event triggers fire when a change is made in any state. My tests were mainly conducted with OnSelect and OnChange field event triggers. I did not test OnLock or OnUnlock.
I was able to work around this by altering my design plan for my application, but it seems like Qlik should allow users to select which state you are polling for changes. It is also important to note that triggers will not cascade, i.e. a trigger will not cause another trigger to fire downstream.
Hi Brian,
Do u get an answer yet?
I am checking for sth similar
Thanks
Based on the tests I've run, it appears field event triggers fire when a change is made in any state. My tests were mainly conducted with OnSelect and OnChange field event triggers. I did not test OnLock or OnUnlock.
I was able to work around this by altering my design plan for my application, but it seems like Qlik should allow users to select which state you are polling for changes. It is also important to note that triggers will not cascade, i.e. a trigger will not cause another trigger to fire downstream.
thanks, i am still using 11.2 sr5
but seem not hearing that such new feature of which event triggers with specified states is available in newer release
I'm currently using v12.0.2 and the feature is still not available. I'll see if there's something new in SR4 and get back to you.
I don't see anything in v12 SR4 either.