function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
C2C2 

Record Choice Set criteria isn't working for a formula field or a checkbox even though documentation indicates otherwise

I am creating a record choice set in a flow and whenever I use a checkbox or a formula field as my criteria, I get no results. This documentation indicates I should be able to use a checkbox field: https://help.salesforce.com/articleView?id=sf.flow_ref_operators_filter.htm&type=5

Anyone else experiencing this issue?
AnudeepAnudeep (Salesforce Developers) 
Can you confirm if there are any records in your that satisfy your criteria of the checkboxes? Record choice sets are nothing but records returned from a query. You can also run a SOQL query in the Developer Console to confirm if you are getting records with all the filter conditions. Maybe there are any records with the same criteria on your instance.

Also, As per the documentation, When you select a checkbox field under Field. If you filter for records whose checkbox field is null, no records are returned.

Also, I read this note

"NOTE When a Checkbox Group or Multi-Select Picklist screen component uses a record choice set, only values from the last record that the user selects are stored in the flow variables. If multiple Checkbox Group or Multi-Select Picklist components on one screen use the same record choice set, the variable assignments obey the first of those fields."

https://help.salesforce.com/articleView?id=flow_ref_resources_recordchoice.htm&type=5

Let me know if this helps, if it does, please mark this answer as best so that others facing the same issue will find this information useful. Thank you
C2C2

Yes, there are record that satisfy my checkbox. Here are some screenshots:SOQL Query


Flow query

I don't believe I am using a checkbox group.

Mindy ReidMindy Reid
Have you ever needed to automatically update a Case when a Task was logged against it? Update Records action via the lookup field because the ID value was Although using custom lookup fields got the job done.

MySainsburys (https://www.mysainsburys.me/)
Priscilla PestoffPriscilla Pestoff
I know this is a few years old, but I just ran into this issue and did not see answers out there. My issue was resolved when checking field level security for any field referenced in the record choice set configuration; that is, not only the condition requirements, but also sorting fields and I would assume the 'store more' fields. It did not throw an error, the choice set was just blank. In my case, I chose the wrong date field in the Sort By that the users did not have access to.