When opening each sheet directly, the behavior works correctly.
However, when users navigate between sheets using the built-in Previous (<) and Next (>) sheet navigation arrows, the selection from the previous sheet remains.
Example:
Software sheet:
SoftwareFYSelect = 2025
Navigate to Cloud sheet using built-in Previous arrow:
Expected:
FYSelect = 2025
SoftwareFYSelect cleared
Actual:
FYSelect = 2025
SoftwareFYSelect = 2025
As a result, selections from both dashboards remain visible.
Questions:
1. Is this expected behavior in Qlik Cloud?
2. Are sheet actions executed when navigating via the built-in sheet arrows?
3. Is there a recommended approach for setting sheet-specific default selections when using built-in navigation?
Sheet Actions are executed when using the builtin arrows. I think what you are seeing is a bit of a non-intuitive sequence issue. "Max(SoftwareFYSelect)" is computed before the Clear state is actually applied to the data. You can see this by manually clearing FYSelect before changing sheets.
You can fix this by adding a {1} to your selection calculation.
Max({1}SoftwareFYSelect)
If that is too broad for your use case you can try:
In Sense, the actions working with selections can be a bit tricky, as the previous step may not take effect when the next one is executed. I'd go with the approach suggested by Rob.
Another option is to avoid sheet actions entirely and use one calendar for both. This will require a bit of data remodelling, though. As an option, you can have a calendar with a year field connected to both Fields.
The other option is to have the year selection field completely disconnected from the data model. Howerver, in your objects you would have to add set analysis like {<SoftwareFYSelect={$(=Max(YearSelectorNewField))}>} or {<FYSelect={$(=Max(YearSelectorNewField))}>}
