Select In Field

[a_mullick]

Hi,

I have an issue with some actions on buttons that set various values in the application. I can't share the main app, but I have mocked up an example to show what is happening (although the 'error' I'm getting here is slightly different to the one in the live app, but the idea is the same).

There is a document level trigger to set set up values on openeing the document, and then the user should be able to click on button 1 or button 2, to set different values depending on what they want to view. What you should notice is that the 'Select in Field' for Week and Day is not applied the first time you click, but it is the second time you click. As I said, this is not quite the problem in the live app, but the idea is the same: it appears that not all 'Select in Field' actions are not applied on the first click.

Is there something wrong with the syntax?

[swuehl · Accepted solution]

What if you change the set identifier in your search expression's aggregation functions from default state to 1, like

=max({1<[Survey ID]={'NSS'}>} Day)

[martinpohl]

two answers:

first from Qlik:

Cascading actions are unsupported.

The other strange behavior:

If you start an action and select the excludes SurveyID all values are grey, an impossible combination from values is done.

Don't know why this is possible but maybe an evidance for solution

Regards

[a_mullick]

Thank you. That certainly seems to work in this case. Unfortunately, I do just that in the live app - the problem in the live case is that [Survey ID] is not set until the user clicks twice.

Regards,

Azam

[a_mullick]

Hi Martin.

Do you have a fuller reference or definition for 'cascading actions are unsupported'?.

Also, I'm not quite sure how you got to the second 'strange behaviour' case. Can you give me the steps you took please, so I can reproduce it?

Many thanks,

Azam

[a_mullick]

I've marked Stefan's answer as correct as technically it is for the example I submitted. Unfortunately, my test example did not correctly capture all the conditions of the live app, so it wasn't a solution I could use, but it may be helpful to someone else.

Martin's answer below I think is closer to the root of the problem and a simple reordering of the sequence of actions has in this instance solved the issue.

Thanks/Vielen Dank