File for Field Trigger

[#1]

Here you go, Nate Brunner and @RichardLowe. Not ideal but hopefully better than what we had.

[natebrunner]

Thanks. Is the only thing you added the Document Level Field triggers? And I'm assuming what that does is add in a few more layers so that hitting Back doesn't immediately undo what was just picked right?

[#3]

Yes and I also added triggers to the second Name field so that you can select Name in either list box and it will change the other field.

[natebrunner]

Right. I saw that. In my case, I'm only making the one field accessible to the user, but I agree with putting it on both.

I'll just toss a note up by date selection that users need to tread lightly and we'll have to train them a bit to watch out for it.

Thanks again for the help.

[#5]

It's definitely not ideal and I would recommend the reference field like we talked about, but in your specific circumstances at least this would be better than before (take a couple Backs to mess it up). I try to avoid triggers like this whenever possible!

[#6]

Sorry for the very delayed response.  Got busy on a bunch of other items, finally getting back to this issue.  I am able to remove the BACK button from within the app on pages where it is an issue.  Luckily there are not many and it really doesn't cause any functionality issue.  (Although would be nice not to have to do this...)

Thanks again!

Richard

[#7]

Hi Richard!

Could you please tell how you disabled 'BACK' button for a specific page?

Thanks in advance for your help!

Elena

[#8]

Hi Elena,

Sorry I just reread my post, I should have been more specific.  I have a custom Back button on pages in the app that we have custom added.  That is the button I can remove on pages where a user could use it and due to field triggers on a page, users would experience unexpected behavior.  (as in it wouldn't go back unless they pressed it more than 1 time)  So I can remove THAT Back button.

However, I have not removed or disabled the built in QlikView application Back button that is on the Navigation Tools bar.  Although, I suppose you can just turn off the Navigation bar but that will turn it off for everything.

Not sure if this answers what you are asking but I hope it helps.  If not, let me know!

[#9]

Richard,

Thanks for a reply!

Yes, that answers my question. I hoped there is a way of prohibiting a user to go back and forward in selection list

I also have triggers to make identical selections in different fields and they, of cause, are messed up by this QV functionality