Skip to main content
Entitlement Process versioning display rules

Entitlement Process; Versioning enbabled; How Entitlement process displayed

Ksawery Lisinski avatar
Written by Ksawery Lisinski
Updated over a week ago

The Entitlement process is an unusual metadata type due to its object-based nature, and the underlying architecture. This article will outline the different approaches for displaying the Entitlement process in certain circumstances.


  • Entitlement processes versioning enabled

How Elements display multiple active and inactive versions of Entitlement processes

In the rare event that there are multiple Entitlement processes int he org, having the same API name (which is possible if those Entitlements Processes are based on different objects), then in case Entitlement Process versioning is enabled, and multiple active/inactive versions are present:

  • The First Entitlement Process (Original) node name, if versioning is enabled, is in the format: “Entitlement process name : Master version : Active/Inactive”

  • If an Entitlement process has versions then the node name format is:
    “'Initial Entitlement process name': ‘Entitlement process version name’: Active/Inactive“

  • The 'active' value is represented in the Name column in the org model following both the original Entitlement process name and the Entitlement process version name

  • We sync the version number into to Summary field and display “Version N of the 'Original Entitlement process name'“

  • When a master version of the Entitlement process isn't present in the org anymore: for all versions of that deleted Entitlement process in the summary field we show “Version N of a deleted Entitlement process“

Not all Entitlement Processes are synced - what to do?

In the event that you have multiple Entitlement Processes having the same API name, the API calls made to Salesforce will only return a single, random Entitlement Process. However, the versions of that Entitlement Process are going to be returned if APi names are different. Unfortunately, this is a Salesforce platform architectural limitation that cannot be handled otherwise.

Did this answer your question?