You are here:
Compatibility Considerations for Processes
Before you design a process, understand how processes interact with other Salesforce features, like custom objects and fields.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
After December 31, 2025, existing processes continue to run, and you can activate, deactivate, and edit them; however, we recommend using Flow Builder. To migrate existing processes, plan your switch to Flow Builder and use the Migrate to Flow tool. For new automations, create flows in Flow Builder.
Objects
Process Builder doesn’t support:
- Deprecated custom objects
- Signup Request—unsupported in schedules only
- Social Post
- Social Persona
External Objects
- External objects aren’t supported in record-change processes.
- When you create or update external object records, don’t set values for indirect lookup relationships that map to a different data type on the external system. For example, don’t set a value for a Text indirect lookup relationship that maps to a Date value on the external system.
Custom Fields
- Process Builder doesn’t support custom fields of type File.
- If a process references a custom field:
- You can’t delete the field.
- If you change the field type or name, the process breaks.
- If you change the field label, the process doesn’t break. But it still uses the original label.
Derived Fields
Process Builder doesn’t support fields whose values are derived from other fields.
Examples of derived fields include Contact.Name,
User.MediumPhotoUrl, and EmailMessage.Name.
Polymorphic Fields
Queue labels
aren't supported in process criteria. For example, you can't use
[Lead].Owner:Queue.Name in process criteria. Instead, use
[Lead].Owner:Queue.DeveloperName to reference the queue's API
name.
Validation Rules
- Scheduled Update Records actions skip validation rules.
- Immediate Update Records actions obey validation rules.
Shield Platform Encryption
You can’t use an encrypted field as a filter in an Update Records action.
Duplicate Rules
If a duplicate is found when a process tries to create or update a record, the process fails.
Converted Leads
To evaluate records that result from converted leads, enable the lead setting Require Validation for Converted Leads.
Formula Field Values
If a standard formula field references a field on a related object, that field's value is always null when a process starts. This limitation doesn’t apply to custom formula fields that reference a field on a related object. For a custom formula field that uses the same formula, the field’s value is derived when a process starts.
For example, the RevenueShare field on Campaign Influence calculates
CampaignInfluence.Opportunity.Amount * CampaignInfluence.Influence.
Because the formula references a field on Opportunity (a related object), the field’s
value is null.
Platform Cache
When a process contains a scheduled action, make sure that later actions in the process don't invoke Apex code that stores or retrieves values from the session cache. The session-cache restriction applies to Apex actions and to changes that the process makes to the database that cause Apex triggers to fire.
