How to Commit and Deploy Custom Settings from a User Story

With Copado you can commit and deploy custom settings metadata and values from a user story. First, you need to commit the metadata to deploy the custom settings object and its fields to the destination org. Then, you can add the custom settings values as a deployment task on the same user story where you have committed the metadata. 

Note: The metadata deployment is only necessary if you don’t have the custom settings object and its fields in the destination org. Otherwise, you just need to deploy the values on the deployment task on the user story.

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.

Let’s take a closer look at the steps to commit and deploy custom settings from a user story: 
  1. Navigate to the User Stories tab and select an existing user story or create a new one.
  2. Fill in the relevant details and click on Commit Changes.
  3. Select the custom settings object and fields you want to commit and click on Commit Changes:
User-added image
 
  1. After the commit is done, navigate to the Deployment Task related list on the user story:
    1. Click on New:
User-added image
  1. Select from the Type drop-down menu: Custom Settings.
  2. Click on the link refresh custom settings to load the list of custom setting objects.
  3. Select a custom setting object from the dropdown.
  4. Click on Get Custom Settings Values (the values are retrieved and listed in the multi-select picklist field) and select the values to deploy.
  5.  Fill in all other relevant fields and click on Save:
User-added image

Note: If you’re deploying the custom settings object and fields along with the deployment task, you need to select After Deployment in Perform Deployment Task.
 
  1. Return to the Details section of the user story and deploy the user story. The user story deployment task becomes a custom setting deployment step when the deployment is created.

How did we do?