Action Limits and Limitations
Actions can work differently than you expect in certain situations and for different objects. Keep these limits and limitations in mind when working with actions.
Required Editions
| Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, Database.com, and Developer Editions |
- Quick actions aren’t available in Aura Experience Builder sites.
- You can display up to 10 actions in Lightning view.
- Custom images used for action icons must be less than 1 MB in size.
- Custom actions can be defined for person accounts but with these exceptions.
- Person account-specific fields, including Email and Mobile, aren’t available in action layouts when using object-specific custom actions to update accounts.
- To set up object-specific custom quick actions that create person account records, define a custom lookup field for Account on the Account or Contact object. Global custom quick actions can be used without defining this field.
- Actions that create business account records from a person account detail page must be global, not object-specific.
- Actions associated with objects that aren’t supported in Lightning Experience don’t appear in the Global Actions menu. Also, the Global Actions menu doesn’t support standard Chatter actions.
- Mobile smart actions don’t appear in the full Salesforce site, regardless of which page layouts you add them to. They appear only in the Salesforce mobile app.
- The Chatter page in Lightning Experience supports only the standard Chatter actions Post, Poll, and Question, and if you have Groups, the Announcement action.
- Quick actions don’t inherit the app’s branding on mobile.
- The palette in the action layout editor doesn’t support:
- Record type fields
- Read-only field types such as roll-up summary, formula, and auto-number fields
- Read-only system fields such as Created By or Last Modified By
- When you create a custom action and the action type is Update a Record, you can't add the Owner field to the action layout for most objects. The exception is Case records. You can add the Case Owner field to your action layout when you create a custom action to update a Case record.
- Actions on the user profile page come from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. Only standard Chatter actions appear on the user profile page, regardless of which actions are assigned to the User Page Layout or the global publisher layout.
- Actions on reports come from the Quick Actions in the Salesforce Classic Publisher section of the global publisher layout. Only standard Chatter actions appear on reports, regardless of which other actions are assigned to the global publisher layout.
- Chatter groups with customers don’t support global create, log a call, or custom actions and display only standard Chatter actions, such as Post, File, Link, and Poll.
- External objects support quick actions, except when the actions involve features or
functionality that are incompatible with external objects. For example:
- Formulas can’t reference fields on external objects, so you can’t reference an external object field to set a predefined field value for a quick action.
- Log a Call actions create tasks, which aren’t available for external objects.
- When you create an object-specific action, you can choose as a target object an event, a task, or any object that has a parent-child or lookup relationship to the host object. You can’t choose Quote as a target object from Opportunity. But to create quotes from an opportunity you can go to the opportunity’s Quotes related list and click New.
- The Account Contact Relationship object supports custom actions, but with limitations.
- Custom actions must be specific to the Account Contact Relationship object. Global actions aren’t supported.
- You can create actions that update records or invoke Lightning components or Visualforce pages. But you can’t create actions that create records.
- You can’t create actions that send emails or log calls because you can't associate activities to the Account Contact Relationship object.
- You can’t override the default actions on the Account Contact Relationship object.
- Only custom actions that are created on the Contact object can use the Account Contact Relationship object as a target object.
- Chatter standard actions aren’t supported because the Account Contact Relationship object doesn’t have a Chatter feed.
Did this article solve your issue?
Let us know so we can improve!
