Components available in change sets
Key Takeaway
Adding a custom object to a change set doesn't bring its custom fields, so add each field you need too. Reports in "Unfiled Public Reports" don't deploy even if you add them, so copy or move them to a different report folder first.
A change set moves metadata, meaning configuration such as objects, fields, layouts, automation and code, from one Salesforce org to another. Not every component type can go in a change set, and some components behave in unexpected ways after they arrive. Knowing what can travel, what can't, and what happens on arrival lets you plan a deployment that works.
Component types you can add
You build an outbound change set by picking components from a list of component types. The types in that list vary by experience and edition. Some components also depend on their related feature being present.
The list covers many kinds of configuration. Here are some examples of each kind:
- Data model: Custom Object, Custom Field, Record Type, Global Value Set, Custom Metadata Type, Custom Setting
- UI: Page Layout, Compact Layout, Lightning Page, Tab, List View, Path Assistant
- Automation and code: Flow Definition, Flow Test, Approval Process, Validation Rule, Workflow Rule, Apex Class, Apex Trigger, Lightning Web Component Bundle, Aura Component Bundle, Visualforce Page
- Security and access: Permission Set, Permission Set Group, Role, Queue, Group, Sharing Criteria Rule, Sharing Owner Rule, Restriction Rule, Scoping Rule, Custom Permission, Named Credential, Remote Site
Some listed types have limits. Embedded Service Deployment covers only standard Chat, not Enhanced Chat. Email Template covers Classic and Lightning templates, including templates made in Email Template Builder.
When you add page layouts, global publisher layouts and Outlook publisher layouts show without their type. Give them distinct names so you can tell them apart.