-
Notifications
You must be signed in to change notification settings - Fork 13
Description
Steps to reproduce:
Create a screen flow with 3 quick choice fields.
Make the data fetcher contingent on the first field being populated, and either of the other fields having a value.
Set the second and third fields to conditionally hide dependent upon the value in the first field.
Execute flow
Result: Fetcher runs, UI displays results and successful assignment. selectedChoiceValues is null. Often selectedChoiceLabels is often null.
Real-world scenario where this came up.
Data setup:
Account data set has > 700k records so need additional criteria to run query
Accounts in the US has > 300k records so need additional criteria to run query
No state has > 50k accounts
Accounts in the UK has 60k records
No constituent country in the UK has > 40k accounts
Picklist 1) Countries
Picklist 2) States in the US
Picklist 3) UK constituent countries
Visibility rules
If country = us, display us state list
If country = uk, display constituent countries list
Fetcher runs if
country = us and state != null OR
country = uk and constituent country != null OR
country != uk and country != us
Set Picklist 1 to US, and select a state -
Search for an account with the fetcher and select it
Click next/finish
Account retrieved by fetcher shows selectedChoiceValues = null and often selectedChoiceLabels = null.
Currently only have managed version deployed in org, and we are trying to go-live tomorrow, so haven't had time deploy unmanaged version to scratch org for further troubleshooting and to pull together a pull request.