Note: It is important to complete this mapping to participant fields so that the Calculated Field will fetch the correct value for the participant in question. Not doing this could lead to incorrect data being queried.This seems pretty important yet the product allows you to proceed without this. Can we either make this required or add a tooltip that references this?
You can use a combination of Field and Value to define the filters.
a. If users select Field, all mapped participants fields can be used.
Ex. The below would need to be filtered so the calculated field only looks at the # of days in onboarding for a specific account. The filter added is account mapped to the account field within AO participants.
This is similar to sending account level reports but when adding reports to an outreach or program it indicates an account or contact mapping is required.
I understand that these filters can be anything and that we can't make it so the product knows if something is missing or won't bring back a single value.
In my specific situation, the customer missed the account filter so it dropped any that got to that specific conditional wait step.
So, my hope is we can make this more user friendly for someone setting up this up for the first time.
Second, to make the Calculated field work right the key point is to make sure that you end up with a single value.
Am I understanding Karl’s statement to mean that this only works on fields with a single value? Does a calculated field not work with fields that store multiple values?