Actions inside a group are not firing

Been banging my head against the wall here on this one, need me some Spock assistance :nerd_face:
Spoke to crush the computer

I’ve got an action, that’s part of a Group of actions that should fire off on the table event action, but for some reason the action I’m having problems with is not following the condition and instead being skipped.

App: TheNASAStudyApp-629466
Action: Alert | No Respondent Selected - part of “Stack | Measure (tapped)”


emulate as “

  1. Starting from the “Home Screen” - tap option 3 (“Continue Ongoing Visit”)
  2. In the Control Panel, select “NS99918” - should be the only option there
  3. Scroll down to the “Remaining Measures” inline view -

When you tap an option you should get a warning about not having something selected (the respondent, from the second action in the stack), but instead I’m getting an alert about consent (the third action in the stack).

Would appreciate if someone could take a look and see if it’s just some condition I’ve got mixed up, or if there’s some bug with Grouped actions?


You’re sure Current_User has only one row?

1 Like

Yes. And I’ve checked that the column is indeed included in the slice’s columns.

1 Like

I’ve also got other actions that are now firing off when they shouldn’t be.

Part of the same stack:

Here’s the condition:

And the formula controlling that column:

This field is blank (the ongoing interactions) so the warning for ongoing actions shouldn’t fire off… yet it does. :face_with_head_bandage:

Any difference?

    index([_thisrow].[Current_PID_Ongoing_Visit], 1) = [Visit_Link],
      [_thisrow].[Current_Respondent] = [Interaction_Respondent]

I’m thinking there’s more going on, see my video from above.

I’ve hard coded a slice to be blank, yet the formula ISNOTBLANK(slice[Column]) is firing off.


No, I tried switching things around inside the SELECT() formula, no change in behavior.

I tried a true root of the core issue test:
I created a new slice, making it empty with a FALSE formula, then a new action that fires off with the new slice is NOT blank - and it didn’t fire.

So it’s something with my logic somewhere… Ugh.

1 Like

count(...) = 0 instead if isblank(...)?

1 Like

@Steve you were right that it was something to do with a technical thing.


that worked. Wrapping the ANY() around the current user slice seems to have done the trick.

I remember Praveen explaining this problem once, something like:

“Because there’s a record for the Current_User[Whatever] slice, technically it’s not blank - even though there are no values in the field - the presence of the record is good enough for the non-specific ISNOTBLANK().”

1 Like

That’s really good to know!