topic Problem with OnAnySelect Trigger and Back and Forward buttons in QlikView

Problem with OnAnySelect Trigger and Back and Forward buttons

pljsoftware — Thu, 07 Apr 2011 15:25:02 GMT

Hi all!

I have noticed a strange behaviour with QlikView 9.0 SR7 64-bit.

If I define an OnAnySelect trigger, with a "Set Variable" action, the "Back" and "Forward" buttons in Selections menu stops working.

I have verified this issue with version 9.0 SR6 too. Is this a bug?

Thanks in advance for the attention.

------------------------------------

Luca Jonathan Panetta

PLJ Software

Problem with OnAnySelect Trigger and Back and Forward buttons

Anonymous — Thu, 07 Apr 2011 15:33:24 GMT

I see how you are thinking, but imo it is not wrong.
The action says "change to Y' on any selection, but it never says that it should change back to X on deselection.

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

pljsoftware — Thu, 07 Apr 2011 15:40:52 GMT

Hello Dennis,

the problem is that the selection in the F1 list is not reverted when I click the BACK button.

Thanks
Luca

------------------------------------

Luca Jonathan Panetta

PLJ Software

Problem with OnAnySelect Trigger and Back and Forward buttons

Thu, 07 Apr 2011 15:45:19 GMT

I see what you're saying, the Back button doesn't do anything at all. Removing the OnAnySelect trigger makes the Back button work again.

Maybe you can try adding a OnSelect Field Event Trigger to the F1 field. This is under the same Document Settings... Triggers tab.

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

pljsoftware — Thu, 07 Apr 2011 16:08:39 GMT

Hi Moshea,

I know that if I remove the OnAnySelect trigger the Back button works again but for my purposes I need to use the OnAnySelect trigger.

Any other ideas?

------------------------------------

Luca Jonathan Panetta

PLJ Software

Problem with OnAnySelect Trigger and Back and Forward buttons

Thu, 07 Apr 2011 16:34:03 GMT

I tired running a macro on OnAnySelect but the problem seems to persist. It looks like a bug to me. The only work around I can find is to do what I mentioned above about using only Field Event Triggers instead of OnAnySelected. I know this is a huge pain if you have a lot of fields, I just can't figure out a way around it.

I even tried making a macro that pressed a button on OnAnySelected and the button ran a macro to set vTest. This still didn't work. Sorry I can't be of more help.

Problem with OnAnySelect Trigger and Back and Forward buttons

Thu, 07 Apr 2011 16:37:05 GMT

Here's another post with the same problem but no solution:

http://community.qlik.com/forums/t/25752.aspx

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

pljsoftware — Fri, 08 Apr 2011 10:36:48 GMT

Hi everybody,

I have contacted Qlikview and they have confirmed that is a BUG.

Regards
Luca

------------------------------------

Luca Jonathan Panetta

PLJ Software

Problem with OnAnySelect Trigger and Back and Forward buttons

Jason_Michaelides — Fri, 13 May 2011 10:55:14 GMT

Not one they've fixed in v10 SR2, unfortunately! I am having the exact same problem in v10SR2. Hopefully in the next release...

Problem with OnAnySelect Trigger and Back and Forward buttons

Fri, 18 Nov 2011 23:23:41 GMT

Persists in v10 SR3 - confirmed bug ID 41442.

Very annoying indeed.

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

Anonymous — Thu, 25 Oct 2012 11:40:03 GMT

Noticed in Desktop version 11.00.11282.0 SR1 (64bit). I've submitted a case.

Is this an isolated issue ? I'm surprised there aren't more discussions about it.

Jonathan

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

pljsoftware — Fri, 26 Oct 2012 17:17:00 GMT

Hi Jonathan,

I have not investigated more about this.

You can test my exemple in QV 11 SR2, now I use always QV 10 SR5.

Regards

Luca Jonathan Panetta

PLJ Software

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

Anonymous — Thu, 01 Nov 2012 11:40:39 GMT

Response from QlikTech support:

"In QlikView 10 and later the Back operation goes back one step from previously applied action. This includes all actions as well as variables.

The problem here is which action should be revertable and which shouldn't. In the case of variables I can see that this in some conditions isn't desirble while in some cases it would be desirble. The most optimal suggestion that I can think of is that you are able to define if an action should be reversable or not. And that would be regarded as an feature request."

I've asked for the feature request suggested. In the meantime however, possible solutions could include:

1. Accepting functionality and explaining to users that working back through their configuration setting selections as well as their field selections is 'as designed'

2. Rework application to not use variables, which are mainly used for:

a. showing elements: May be able to do Action triggers to restore and activate sheet objects that are otherwise mimised, using containers where I have groupings of sheet objects

b. determining what will be shown in charts, in terms of date ranges and what is to be compared against: Not sure how I can achieve these other than through variables.

3. Find a way of overriding the navigation buttons, to interupt their normal operation and simulate the previously navigational features that were limited to going back and forwards: No idea how I would achieve this and suspect it would take maintenance to keep it working with subsequrnt QV releases.

Any ideas on points 2b and 3 would be most appreciated ?

Jonathan

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

pennetzdorfer — Mon, 23 Sep 2013 09:48:45 GMT

Any news on that topic?

Re: Problem with OnAnySelect Trigger and Back and Forward buttons

punitpopli — Mon, 03 Nov 2014 14:05:19 GMT

Panetta Luca Jonathan :

Hi,

I was also facing the same issue with Triggers and back button and have tried double clicking on the back button and this action will take me to the previous selection.

Could you please also try the same and let me know if this work for you?

Thanks,

Punit