Deployment Step: Full Profiles

Updated 3 months ago by Copado Solutions

This article is part of the Deployment Steps.

The Full Profiles deployment step lets you deploy a profile with all its properties from one org to another using the Metadata API.

The term full profiles is used in Copado  to refer to the retrieve of profiles in which Copado does a full description of your organization in order to ensure every single property of the profile is included in the deployment. Some of the properties included in a profile are user permissions, field level security, object level security, tab visibility, record type visibility and layout assignments.

To create a Full Profiles deployment, create an Advanced (multi-step) deployment and add a Full Profiles step:

During the deployment, profiles are automatically cleaned by removing any components that do not exist in the destination org (by retrying) and preventing the deployment from failing. The engine retries until it gets a successful deployment or gives up after 400 retries.

To deploy specific properties of a profile instead of the entire profile, you can use the MetaData step, where the specific properties of a profile that get deployed will be relative to the set of metadata included in the same step (e.g. custom fields, custom objects, record types, layouts, etc).

How did we do?