CommunityDevOps ExchangePartners
10 minutes

Why Change Sets Suck (the Time out of your DevOps Process) – Part 2

Written by
Jen Nelson
Table of contents

Hello, #AwesomeAdmins! 

In our last post, Why Change Sets Suck (the Time out of your DevOps Process) – Part 1, we looked at the limitations of native Change Sets solved by Copado including Version Control, Release Pipeline structure and cross-Stack Deployments.

As mentioned previously, there are many limitations to native Change Sets, and Copado resolves all of them!

In Part 2 of our 3-Part Series, we are going to focus on Deploying Standard Components, Standard Settings,Custom Settings with Values and Quality Control.

Native Change Sets do NOT include Standard Metadata

When searching for Metadata Components to add to a native Change Set, there are no Standard Metadata Components available for Selection. 

That means, for example, any changes that you have made to Standard Fields, including modification of Standard Value Sets, as well as Standard Layouts, Standard List Views and Standard Objects cannot be included in a native Change Set.

Instead, you must manually track these Standard Metadata Component changes and manually update each Salesforce Environment accordingly.

Copado uses the Salesforce Metadata API and all Supported Metadata

Any Metadata Component supported by the Salesforce Metadata API is available for selection in the Copado Metadata Grid on Commits and Deployments.

Notice in the Copado Metadata Grid example shown below how none of the Components that I have selected have __c at the end of the Component Name…that means that everything I have selected below is a Standard Component!

Gone are the days of having to manually track and update:

  • Changes to Standard (native) Page Layouts
  • Changes to Standard (native) Fields
  • Changes to Standard (native) ValueSets; examples of StandardValueSet would be the Type or Industry Picklist Values on the Account Object
  • Changes to Standard (native) List Views
  • Changes to Standard (native) Lookup Filters
  • Changes to Standard (native) Search Layouts

Native Change Sets do NOT include Custom Settings Values

While a native Change Set does allow us to select a Custom Setting and the Custom Setting’s Metadata:

We are only able to retrieve the Metadata, not the actual Values that we have defined behind the Custom Settings’ “Manage” button:

Copado will Commit Custom Settings Metadata and Deploy Custom Settings Values

With Copado, we can not only select the Custom Settings Metadata in our out-of-the-box Metadata Grid:

But we can also add a Deployment Task (aka Deployment Step) of Type “Custom Setting” to our User Story, so that we retrieve the Custom Settings Values we have defined in “Manage”:

No more having to track our Custom Settings Values manually and no more having to manually update each Salesforce Environment with our Custom Settings Values!

Native Change Sets do NOT include any Standard Settings

With native Change Sets, you will need to manually track any changes you make to all Standard Settings and you will need to manually update those Standard Settings in each Environment as you move up your Release Pipeline:

As of this writing, Salesforce’s Generally Available API is v47 (Winter ‘20) with v48 (Spring ‘20) in Preview Sandboxes.

Depending on your Salesforce Edition, as well as Features enabled in your Orgs, there are potentially 90+ Standard Settings included in the Salesforce Metadata API and, if any of these 90+ Standard Settings were changed as part of your DevOps Process, you are unable to include these Standard Settings in native Change Sets and would, instead, have to manually track and update these Standard Settings on each Salesforce Environment.

Copado’s Metadata Grid supports all Metadata supported by the Salesforce Metadata API – including Standard Settings

With the Copado Metadata Grid, all Standard Settings in the Salesforce Metadata API are available for selection.

Native Change Sets do NOT include any Quality Control of Metadata Changes Deployed that is not natively required by the Platform

The only quasi-Quality Controls available in native Change Sets are the native Salesforce Platform-required Apex Tests with Code Coverage and Validation-only Deployments.

Copado includes extensive Quality Gates

The only quasi-Quality Controls available in native Change Sets are the native Salesforce Platform-required Apex Tests with Code Coverage and Validation-only Deployments.

Copado Quality Gates can be run from User Stories, but oftentimes can also be run from an Org Credential to include a complete Environment (on-demand or as a Scheduled Job), or as Quality Gates in Copado Continuous Delivery.

Native Salesforce Quality Gates

  • Apex Tests with Code Coveragebonus, Copado allows us to set Minimum Code Coverage Thresholds for each Salesforce Environment in our Release Pipelines
  • Validation-only Deployments
  • Native Salesforce Automations (SFA) including Approval Processes, Validation Rules, Workflows, Process Builders/Flows and Rollup Summaries, to name a few

Out-of-the-Box Quality Gates

Add-on Quality Gates

  • Copado Selenium Testing – Automated Selenium Regression Testing on Platforms such as Sauce Labs, BrowserStack or Cross Browser Testing
  • Copado Compliance Hub – a custom Rules Engine to scan key Metadata Components such as Profiles or Permission Sets for violations such as View All Data/Modify All Data being exposed to Non-System Administrator Profiles


Native Change Sets Limitations Addressed by Copado

  • Native Change Sets only cover a single-step in a Complete DevOps Process.
  • Create–>Test–>Deploy–>Release–>Monitor–>Plan
  • Native Change Sets have no Version Control.
  • Native Change Sets do not allow for any Release Pipeline structure nor cross-Stack Deployments.
  • Native Change Sets do not allow inclusion of any Standard Components, Standard Settings nor Custom Settings.
  • Native Change Sets have no Quality Gates to ensure that the Metadata being Deployed is of high quality and is compliant.
  • Copado covers the end-to-end DevOps Process and is 100% native to Salesforce.


Learn more about Copado’s Solutions By DevOps Stage.

Stay tuned for Part 3 of our 3-Part Series which will cover:

  • Pre- and Post-Deployment Steps
  • Seeding Sandboxes, Deploying Test Data and/or Deploying Data-as-Configuration-Data
  • CI/CD Automation

Want to learn more about Copado?

Here’s some additional Resources for all my #AwesomeAdmin Ohana:

Want to join the Team?

Book a demo

About The Author

Director, Product Enablement

Jen Nelson is a 20-year veteran of the Salesforce ecosystem, a current Salesforce MVP Hall of Fame member and has 30+ years experience in DevOps. Jen has been with Copado for 4 years and is the Director of Product Technical Enablement.

Enhancing Customer Service with CopadoGPT Technology
What is Efficient Low Code Deployment?
Copado Launches Test Copilot to Deliver AI-powered Rapid Test Creation
Cloud-Native Testing Automation: A Comprehensive Guide
A Guide to Effective Change Management in Salesforce for DevOps Teams
Building a Scalable Governance Framework for Sustainable Value
Copado Launches Copado Explorer to Simplify and Streamline Testing on Salesforce
Exploring Top Cloud Automation Testing Tools
Master Salesforce DevOps with Copado Robotic Testing
Exploratory Testing vs. Automated Testing: Finding the Right Balance
A Guide to Salesforce Source Control
A Guide to DevOps Branching Strategies
Family Time vs. Mobile App Release Days: Can Test Automation Help Us Have Both?
How to Resolve Salesforce Merge Conflicts: A Guide
Copado Expands Beta Access to CopadoGPT for All Customers, Revolutionizing SaaS DevOps with AI
Is Mobile Test Automation Unnecessarily Hard? A Guide to Simplify Mobile Test Automation
From Silos to Streamlined Development: Tarun’s Tale of DevOps Success
Simplified Scaling: 10 Ways to Grow Your Salesforce Development Practice
What is Salesforce Incident Management?
What Is Automated Salesforce Testing? Choosing the Right Automation Tool for Salesforce
Copado Appoints Seasoned Sales Executive Bob Grewal to Chief Revenue Officer
Business Benefits of DevOps: A Guide
Copado Brings Generative AI to Its DevOps Platform to Improve Software Development for Enterprise SaaS
Celebrating 10 Years of Copado: A Decade of DevOps Evolution and Growth
Copado Celebrates 10 Years of DevOps for Enterprise SaaS Solutions
5 Reasons Why Copado = Less Divorces for Developers
What is DevOps? Build a Successful DevOps Ecosystem with Copado’s Best Practices
Scaling App Development While Meeting Security Standards
5 Data Deploy Features You Don’t Want to Miss
Top 5 Reasons I Choose Copado for Salesforce Development
How to Elevate Customer Experiences with Automated Testing
Getting Started With Value Stream Maps
Copado and nCino Partner to Provide Proven DevOps Tools for Financial Institutions
Unlocking Success with Copado: Mission-Critical Tools for Developers
How Automated Testing Enables DevOps Efficiency
How to Keep Salesforce Sandboxes in Sync
How to Switch from Manual to Automated Testing with Robotic Testing
Best Practices to Prevent Merge Conflicts with Copado 1 Platform
Software Bugs: The Three Causes of Programming Errors
How Does Copado Solve Release Readiness Roadblocks?
Why I Choose Copado Robotic Testing for my Test Automation
How to schedule a Function and Job Template in DevOps: A Step-by-Step Guide
Delivering Quality nCino Experiences with Automated Deployments and Testing
Best Practices Matter for Accelerated Salesforce Release Management
Maximize Your Code Quality, Security and performance with Copado Salesforce Code Analyzer
Upgrade Your Test Automation Game: The Benefits of Switching from Selenium to a More Advanced Platform
Three Takeaways From Copa Community Day
Cloud Native Applications: 5 Characteristics to Look for in the Right Tools
Using Salesforce nCino Architecture for Best Testing Results
How To Develop A Salesforce Testing Strategy For Your Enterprise
What Is Multi Cloud: Key Use Cases and Benefits for Enterprise Settings
5 Steps to Building a Salesforce Center of Excellence for Government Agencies
Salesforce UI testing: Benefits to Staying on Top of Updates
Benefits of UI Test Automation and Why You Should Care
Types of Salesforce Testing and When To Use Them
Copado + DataColada: Enabling CI/CD for Developers Across APAC
What is Salesforce API Testing and It Why Should Be Automated
Machine Learning Models: Adapting Data Patterns With Copado For AI Test Automation
Automated Testing Benefits: The Case For As Little Manual Testing As Possible
Beyond Selenium: Low Code Testing To Maximize Speed and Quality
UI Testing Best Practices: From Implementation to Automation
How Agile Test Automation Helps You Develop Better and Faster
Salesforce Test Cases: Knowing When to Test
DevOps Quality Assurance: Major Pitfalls and Challenges
11 Characteristics of Advanced Persistent Threats (APTs) That Set Them Apart
7 Key Compliance Regulations Relating to Data Storage
7 Ways Digital Transformation Consulting Revolutionizes Your Business
6 Top Cloud Security Trends
API Management Best Practices
Applying a Zero Trust Infrastructure in Kubernetes
Building a Data Pipeline Architecture Based on Best Practices Brings the Biggest Rewards
CI/CD Methodology vs. CI/CD Mentality: How to Meet Your Workflow Goals
DevOps to DevSecOps: How to Build Security into the Development Lifecycle
DevSecOps vs Agile: It’s Not Either/Or
How to Create a Digital Transformation Roadmap to Success
Infrastructure As Code: Overcome the Barriers to Effective Network Automation
Leveraging Compliance Automation Tools to Mitigate Risk
Moving Forward with These CI/CD Best Practices
Top 3 Data Compliance Challenges of Tomorrow and the Solutions You Need Today
Top 6 Cloud Security Management Policies and Procedures to Protect Your Business
What are the Benefits of Principle of Least Privilege (POLP) for My Organization?
You Can’t Measure What You Can’t See: Getting to know the 4 Metrics of Software Delivery Performance
How the Public Sector Can Continue to Accelerate Modernization