Using RecordType Name In Declarative Tools

 Just a quick hit to say that for some reason, when using declarative tools, when drilling into a Record Type Name, it gives two versions of the Name:

The 1st one resolves to RecordType.Name and the second to RecordType.DeveloperName. The process will fail in many cases if you use the regular Name; try using the "Record Type Name."


Popular posts from this blog

"Disjunctions not supported" - Why Custom Metadata and Flow Don't Mix

What Happens To "Inflight" Process Builders When You Activate a new Version?

Custom Lookup For Flows to Avoid "Disjunctions Not Supported"