Understanding Multiselect Picklists in Salesforce
Multiselect picklists in Salesforce can be tricky to work with, especially when it comes to triggering journeys in Marketing Cloud. The values in these picklists are stored in a specific format, which can affect how they are evaluated in journey triggers.
Troubleshooting the Issue
To troubleshoot the issue, it is essential to understand that the journey trigger will only work if the values match exactly. This means that if you have options A, B, and C, and you want the journey to trigger off option B, you need to list out all the possibilities, such as A; B, A; B; C, B; C, or just B.
The root cause of the issue is the way Salesforce stores and evaluates multiselect picklist values, which can lead to mismatches and prevent journey injection.
Workarounds and Solutions
One possible workaround is to update a value in a different text-based field, which can then trigger the journey. This approach allows Marketing Cloud to process the record and inject the contact into the journey.
Example AMPscript code
/* Example AMPscript code to update a text-based field */
var fieldValue = "Option B";
updateData("Text_Field", "Contact_Key", fieldValue);
Heads up: Make sure to test your journey trigger and update methods thoroughly to ensure they work as expected.
Checklist for Troubleshooting Multiselect Picklist Issues
Troubleshooting Steps
- Verify that the multiselect picklist values match exactly
- Try updating a value in a different text-based field to trigger the journey
- Check the length of the combined values to ensure it does not exceed the limit
- Test your journey trigger and update methods thoroughly
- Consider using a different field type, such as a checkbox or radio button, if possible
Frequently Asked Questions
What is the maximum length for combined multiselect picklist values?
The maximum length for combined multiselect picklist values is 255 characters.
Can I use a multiselect picklist to trigger a journey in Marketing Cloud?
Yes, but you need to ensure exact matching of values and consider workarounds like using a text-based field to trigger the journey.
How do I update a value in a different text-based field to trigger a journey?
You can use AMPscript to update a value in a different text-based field, which can then trigger the journey.
What are some alternative field types I can use instead of multiselect picklists?
You can consider using checkbox or radio button fields, which can be easier to work with in journey triggers.
Need help shipping this in production?
Genetrix builds and untangles Salesforce Marketing Cloud and Agentforce setups for teams that want it done right the first time. If anything in this post sounds familiar, talk to us before it ships.