Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Announcements
QlikWorld, June 24-25, 2020. Free virtual event for DI and DA gurus. Register Today
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Alternate states, triggers OnActivateSheet and distribution

Hi guys,

Let me explain issue we're facing with using alternate states, triggers OnActivateSheet and distribution concurrently.

QlikView document has triggers OnActivateSheet that make selections on fields in some alternate states. This QlikView document is reloaded and distributed to folder to be accessed from Web.

The issue is:

When document is already opened in web and distribution happens - according to audit log - triggers OnActivateSheet apply. BUT, for some reason, they apply on default state instead of taking into consideration alternate states. The whole application is broken in result because default state is corrupted.

Do you have any suggestions or maybe it is reported bug?

Thanks in advance.

3 Replies
Highlighted
Partner
Partner

Re: Alternate states, triggers OnActivateSheet and distribution

Hi

First, are you using WebView (ajax) as client? OnActivateSheet triggers doesn't work then.

I am using triggers on alternate state and it works. Can you give more specific info on what your code does?

Highlighted
Not applicable

Re: Alternate states, triggers OnActivateSheet and distribution

Hi Jerry,

Thanks for reply.

Those triggers do not work when you go from one sheet to another - using actions on buttons, e.g.

We are using Ajax and OnActivateSheet triggers work when you open specific sheet (we need this to set default state of each sheet when document is already opened). And taking into consideration audit log - triggers work when document is being updated after distribution.

Haven't you faced such issue?

Highlighted
Partner
Partner

Re: Alternate states, triggers OnActivateSheet and distribution

Hi

Have you tried hide the tabrow and using buttons instead to navigate?

Doing that you can use triggers to set initial state.

That is how we do it.