I think the reason is...
>that while button 1 is selected... the options of button 2 and 3 are not in the "possible set".
So with setAnalysis the expressions should be changed so this is circumvented.
I'll try (as far as time allows me) to give an example to fix.
What you can do to analyse your problem is
- add 3 textboxes (one next to each button)
- add the select in expression in it...
- and when you've don that,play with the buttons
- then you'll understand my mentioned issue
- this can be fixed by changing the expression so they ignore the selections
I must admit that I have difficulties in getting it right.
Your expression also has the problem that it only works when button 1 is pressed OR all selections are cleared.
I feel like some nested aggregations are needed here... At least the textboxes give a clear hint why it doesn't work
Any others (setanalysis guru's) with ideas?
Additionally, I'm not sure if it is a bug (buhh!)
Because in the actions, you first clear the fieldselection... When you would do that manually, your buttons would work in 1 click (instead of 2).
Perhaps someone can shed some light on this behavior...
Yay! It works!
Check this expression
//change below for the 3 buttons <1 =1 and >1
Note that only 1 action is needed. You can skip the "clear field selections" action...
Let me know if it also works on your side.