Custom Settings Deployment

Updated 5 months ago by Copado Solutions

The Custom Settings step allows you to deploy the data held in custom settings' objects. Ids such as that of users, profiles and the organization Id for hierarchy custom settings are also mapped in the destination environment.

To create a new custom setting deployment follow the steps below:

  1. Go to the Deployments tab and create a new Advanced (multi-step) deployment.
  2. Give your deployment a name and select a source and a destination organization.
  3. Add a new step and select Custom Settings as step type:

  1. Click on the link refresh custom settings to load the list of custom settings objects.
  2. Select a custom setting object from the dropdown.
  3. Click on Get Custom Settings Values (the values are retrieved and listed in the multi-select picklist field).
  4. Select the values to deploy.
  5. Save the step.

If you have not already deployed the custom settings object in the destination organization, you will first need to create a MetaData deployment step to deploy the object and any fields included in it. Once these are deployed, you can go ahead and deploy the values with the Custom Settings deployment.

If the custom settings reference values that are specific to an environment, Copado can automatically change the values of the source environment for the corresponding values in the destination environment. This is done with the Environment Variables feature.

E.g. Environment Variable:

Source Org: AdminUser = "admin.user.dev@company.com"

Destination Org: AdminUser = "admin.user.test@company.com" 

In the custom setting fields, any occurrences of "admin.user.dev@company.com" will be replaced with the value in the destination org: "admin.user.test@company.com".

Alternatively, you can add a from suffix and a to suffix and Copado will replace the from suffix with the to suffix in the destination organization.

E.g. If you are deploying from dev1 to uat and add dev1 in the From suffix field and uat in the To suffix field, adminuser@company.com.dev1 will be replaced with adminuser@company.com.uat in the destination organization. 

In order to ensure the suffix is correctly appended or replaced in the destination organization, add the suffix without the dot:
.uat x 
uat√


How did we do?