Print this page

Using CONTAINS with multiple comma separated values doesn't trigger PB or Flow

Knowledge Article Number 000214160
Description

Passing multiple comma separated values against the CONTAINS operator in the same condition doesn't evaluate the Process/Flow as intended.

Example Process:
Set Filter Conditions: 
[Case].Contact.Email   CONTAINS   someone@company.com,someoneelse@company.com

The above example process will not evaluate as intended because it includes multiple values separated by a comma. 

Resolution

The Lightning Process Builder and Flow do not support comma-separated values in rule criteria. In order to get this functionality to work with the Process/Flow criteria can be modified to only use one value per Filter Condition and add additional Filter Conditions as needed ensuring that each Filter Condition is grouped together with an OR Filter Condition.

Workaround:
Using the same condition as above:

Set Filter Conditions: 
1) [Case].Contact.Email   CONTAINS   someone@company.com
2) [Case].Contact.Email   CONTAINS   someoneelse@company.com

Filter Conditions (
Customize the filter logic):
(1 OR 2) 





promote demote