Gain more control and flexibility with profile, record type and translation deployments

Previously, when deploying profiles or record types, you typically need to select the related components (fields, picklist values, ...) that will go together with the profiles or record types. It was not possible to deploy Profiles without deploying the related components together.

In this release, we introduce a new deployment option "Support component exclusion when deploying record types or profiles". Enabling this setting would allow you to exclude the related components from the final package so that you can deploy just the record types or profiles without being mandated to deploy the fields or picklist values.

Screen_Shot_2019-03-05_at_5.19.00_PM.png

After you enable the option above, a new column "Exclude" will be shown in the "Components Selected" list. In the example below, the profile field level security permission for Rating__c field will be deployed. The field itself, however, will not be included in the final deployment package.

Screen_Shot_2019-03-05_at_5.11.08_PM.png

The above behavior is applied to both org-to-org deployments as well as org-to-git commit flow.

Did this answer your question?