Field Event Trigger vs Back Action

[rishimessi19]

Hi

I have the following data:

Year	Projected Year
2015	2015
2015	2016
2015	2017
2015	2018
2015	2019
2015	2020
2015	2021
2015	2022
2015	2023
2016	2016
2016	2017
2016	2018
2016	2019
2016	2020
2016	2021
2016	2022
2016	2023
2016	2024

Requirement:

1. I need to display 2 filters:

• "Year"
• "Projected Year"

2. Both filters must be "Always one selected" filters.

3. "Projected year" must always only display the possible values of the year selected in the "year" filter.

4. Projected year default selection must always be the most latest year. e.g for "Year"=2015 "Projected Year" must be defaulted to "2023" and for  "Year"=2016"Projected Year" must ne defaulted to "2024"

Challenges I am facing:

1. No able to show the possible values in "Projected Year" based on the "Year" filter selection.

2. I tried using field event trigger to select the most latest year in the "Projected Year" but this is affecting the Back Button functionality. Somehow QlikView is considering the trigger action as a separate action and therefore I need to click on Back button twice to achieve the previous state.

Please provide guidance.

[neelamsaroha157]

Try this

1.

2.

3.

[rishimessi19]

Hi

By using field event triggers, I am loosing the back button (I have a back button on my dashboard) functionality. So, whenever the trigger is applied, I need to click on back button twice to return to the previous state.

[jonathandienst]

Perhaps your interface will work better if you remove the 'always one selected' option from Projected Year. And if you set the latest Projected Year in the expression filter (using set analysis, and override the year)

{<[Projected Year] = {"$(=(Max([Projected Year]))"}, Year=>}

then you would not need a trigger at all.