I’m being asked to create an A-List client list that includes contacts that have 5 different options in a “multiple checkboxes” property selected in their contact card. Is this possible?
Hi @EBrown4 Yes, this is possible.
I’m not sure if you’re looking to find the contact that has all 5, or one of 5, here’s how to do both.
All 5:
Any of 5:
When you create the list, choose the filter for Contact Properties:
Then search for your property:
Then choose your filter criteria:
There are a ton of options for multiple checkbox properties so you have a lot of flexibility with configuring the filters.
I hope this helps, let me know if you have questions!
Thank you Jennifer. The Multi checkbox has prob around 80 options. What I’m after is a list that includes all contacts that have 5 or more of the boxes checked. They can be any boxes, just needs to be 5 or more. Is there a solution for this? I don’t seem to be able select based on this.
Hi @EBrown4 thank you for the additional details, that is definitely a little more complicatd, although I think it could be done.
Do the contacts have the 5 boxes checked all at once, or does the data change over time?
Will change over time. Thank you!
thanks for confirming @EBrown4, I’ll need to do some testing and will let you know if I find a way when I’m back at work tomorrow 
Thanks very much - really appreciate you looking into this for me.
You’re welcome @EBrown4, happy to help find a solution for this!
There are two options I could come up with:
1 - use custom code in a workflow that will return the output with true/false for a custom property and convert the multi-checkbox into an array.
Based on the size of the array, it will determine if the count is equal to 5 and then return true or false to the custom property.
There would need to be a branch to determine whether it’s enrolled in the list or not.
The trigger for the workflow would be based on the property to check in real time if it is 4 vs 5 checkboxes.
This solution would require a developer to build out the workflow with custom coded actions.
2 - use the initial API that is checking for the options in the checkbox to update the property with 80 choices and use that to update 5 other custom properties too.
The basic setup would be:
Create 5 rich text field custom properties (checkbox known value 1, checkbox known value 2, etc.)
Update the API to search the 80 options and when it reaches the first True value for the first checkbox, it would copy that value to checkbox known value 1.
It would continue to search the 80 options to return any values to the corresponding custom option.
You’d need to have it check whether each checkbox known value 1 is “known” and if it’s a match for the new value, if not, it would move to the next checkbox and so on.
These 5 custom properties would be part of an active list, essentially adding each one as a filter that says “checkbox known value 1” is “known” and as long as the contact has all 5, they’ll be added to the list.
…
There is another thought around this - depending on what you’re tracking in the 80 options, you could create custom properties for the individual values and use that to build a lead scoring model.
I’m not sure what these 80 values are or why having 5 is triggering an email, just wanted to throw it out there that you could use the data from your other system differently than how it exists currently.
I hope this helps!