Components available in change sets
Key Takeaway
Only certain component types can go in a change set, and it must contain every interdependent component that doesn't already exist in the target org.
A change set sends customizations, called components, from one Salesforce org (the originating org) to another (the target org). Only certain component types can be added, some go only as dependencies of other components, and several behave differently after they arrive. If you know which components are available and how they arrive, you can build a change set that deploys cleanly and does what you expect.
Components you can add
Which components you can add to a change set varies by experience and edition. Some components also depend on a matching feature.
The component types you can add include these groups:
- Data model and UI: Custom Object, Custom Field, Validation Rule, Record Type, Page Layout, Compact Layout, Field Set, Lightning Page, List View, Tab, App, Button or Link, Action, Path Assistant, Global Value Set, Custom Metadata Type, Custom Setting, Custom Label.
- Automation: Flow Definition, Flow Test, Approval Process, Workflow Rule, Workflow Field Update, Workflow Email Alert, Workflow Task, Workflow Outbound Message, Assignment Rule, Auto-Response Rule, Escalation Rule, Duplicate Rule, Matching Rule.
- Security: Permission Set, Permission Set Group, Custom Permission, Role, Group, Queue, Sharing Criteria Rule, Sharing Owner Rule, Restriction Rule, Scoping Rule.
- Reporting and content: Report, Dashboard, Custom Report Type, Reporting Snapshot, Folder, Document, Static Resource, Email Template (Classic and Lightning, including templates made in Email Template Builder).
- Code and integration: Apex Class, Apex Trigger, Visualforce Page, Lightning Web Component Bundle, Aura Component Bundle, Named Credential, External Credential, Remote Site, External Data Source.
You can also add Embedded Service Deployment, but only for standard Chat, not Enhanced Chat.