Salesforce Fact #422 | Matching rule details in screen flow

Do you know there is an object MatchingRule in Salesforce which stores the details of all the matching rules in the org. So we can use this object in screen flow to get the details and show the same to the user.

Attached are the screenshots.









 


Note: There is a field named SobjectSubType on MatchingRule object which can have either 'None' or 'PersonAccount' as value. If the rule is for a PersonAccount, the value is automatically set to 'PersonAccount' else it is 'None'. However, for standard matching rules present in the org, the field is blank.

For more details, check out: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_matchingrule.htm

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