Salesforce Fact #681 | Null check on screen flow dependent picklist

Screen input component values are set to null when they're hidden by conditional visibility. But hidden picklists in a dependent picklist component aren't set to null unless the entire dependent picklist component is hidden.

In this example, we have a dependent picklist component and a text input component in the screen flow. We have hidden the text component and also we are not selecting the third level picklist value i.e. it is hidden as well. 

When we are doing a null check, for picklist value it is not equal to null whereas for the input text it is set as null.

Reference: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_dependentpicklists.htm&type=5

Attached are the screenshots.





Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #192 | Call batch apex from flow

Image
Generally apex batch jobs are scheduled to run at particular time intervals. But suppose we have a use case where we need to run the batch job on adhoc basis. We can call the batch apex from a screen flow in that case and the screen flow can be invoked from a button. So, the batch job can be executed on demand. Attached are the screenshots.
Read more

Salesforce Fact #457 | Get current user role name in flow

Image
In apex, in order to get the current user role name we need to query the UserRole object. We cannot get it directly using UserInfo object since it has only one method related to role i.e  getUserRoleId(). Using this Id returned we can get the data from UserRole object. But that is not that complex in flow. In case of flow, we can directly get the current user role name using the syntax: {!$UserRole.Name}. Attached are the screenshots.
Read more