Skip to main content

Deploy Managed Package Changes with Copado Essentials

A tailored guide to help with managed package deployments

J
Written by Jeff McEvoy
Updated this week

Managing managed packages doesn't have to be complicated! Copado Essentials makes it straightforward to deploy and upgrade your Salesforce managed packages across environments. Let's walk through everything you need to know to deploy managed packages like a pro.

What You Need to Know First

Before we dive in, here's key thing to understand about managed packages: they're designed to be upgraded, not downgraded. Think of it like updating an app on your phone - you can move forward to newer versions, but rolling back requires uninstalling and reinstalling. This is how Salesforce works across the board, not just in Copado!

Managed packages (1GP) are mostly read-only and closed-source, but here's the good news - you can still make some customizations like adding fields to managed package objects. These customizations live separately from the package itself, so you get the best of both worlds: package integrity and flexibility.

Three Ways to Deploy Your Managed Packages

  1. The Standard Approach (Perfect for Most Cases)

    This is your go-to method for most managed package deployments:

    Step 1: Get Started

    • Jump into your Copado Essentials account

    • Select Deployments and hit "New Deployment" on the right side

    Step 2: Set Things Up

    • Give your deployment a name that makes sense (trust us, future you will thank you!)

    • Pick your Source and Target Orgs

    • Want to track this in JIRA or Azure? Tag it now.

    Step 3: The Magic Moment

    • After clicking Save, under "Add components", find what you need for this Deployment

    • Here's the crucial part: Check that "Include managed package" checkbox! This is your golden ticket to seeing and including managed package components

    • Look for the "Installed Packages" component type and add the relevant options to your Deployment

    Step 4: Don't Forget the Dependencies

    • Got picklist changes? Page layout tweaks? Make sure to include any related components that are related to your managed packages.

    Step 5: Test Drive Before You Go Live

    • Always validate first (seriously, always!)

    • Once your Validation passes, hit "Deploy" and watch the magic happen


    ​

  2. The Pipeline Pro Method (For the Version Control Enthusiasts)

    Love having everything tracked and organized? This one's for you:

    • Create a Work Item that includes your "Installed Packages" components

    • Let the work-item pipeline do its thing - it'll automatically commit the package version to your Git repos

    • You get better version control and a complete audit trail. Win-win!
      ​
      ​

  3. The Git Repository Route (When Your Source Org Doesn't Have the Package)

    Sometimes you need to deploy a package that isn't installed in your source environment. No problem:

    • Deploy directly from a Git repository containing the package declaration

    • Perfect for those "I need to deploy this but don't have it installed locally" moments

Scaling Up: Multiple Target Organizations Made Easy

For a Handful of Orgs (2-20 Organizations)


​Create multiple deployments or work items through Copado Essentials

  • This straightforward approach works perfectly when you're managing a smaller number of environments. You'll have full visibility into each deployment, can handle any org-specific quirks, and maintain complete control over timing. It's also great when you're getting familiar with the process - you'll learn something from each deployment that makes the next one smoother.

For Large Scale Operations (50+ Organizations)

When you're managing dozens or hundreds of orgs, robust automation outside of Essentials may be a more practical solution than individual deployments:

  • Write a Python Script for Automation

    Perfect when you need smart deployment logic - like deploying to sandboxes first, then production orgs based on your business schedule. Great for handling complex scenarios and integrating with your other business systems.

  • Leverage Salesforce CLI for Bulk Operations

    Your go-to choice when you need to deploy the same package to many similar orgs quickly. If your team already uses Salesforce CLI, this keeps everything consistent and familiar.

  • Package Authors: Salesforce's Push Updates Feature

    If you're the one publishing the managed package, this is your secret weapon. Let Salesforce handle the heavy lifting of deploying to all your customers at once - especially useful for critical updates.

Which Approach Should You Choose?

Start with the manual approach even if you think you'll need automation later. It helps you understand your deployment patterns and catch any gotchas before you automate them. You can always graduate to automation once you know exactly what you need!

Common Errors When Things Don't Go as Planned (And How to Fix Them)

The Dreaded ActiveRSS Error

You've tried to deploy a managed package through a method listed above but came across this error:

Required field is missing: activateRSS

Don't panic! This is actually very common and easy to fix. Here's your solution:

  1. In your Deployment, go to Deploy Options > Advanced Options > Find & Replace

  2. Add this handy rule:

update_activate_rss:
  file_filters:
    - '*.installedPackage'
  replace_rules:
    - find: '<activateRSS xsi:nil="true"/>'
      replace: '<activateRSS>false</activateRSS>'

This snippet acts like autocorrect for your deployment - it automatically fixes a formatting issue with the activateRSS field that would otherwise cause your managed package deployment to fail. Just paste it into the Find & Replace section of your Deploy Options and Copado handles the rest!

Pro Tips for Managed Package Success

🎯 Always Validate First: Think of validation as your safety net. It catches issues before they become problems.

📝 Use Pipeline Integration: Work items with pipelines give you that professional-grade version control you'll appreciate later.

🔗 Mind Your Dependencies: Take a moment to review what else needs to come along for the ride.

🧪 Test in Sandbox First: Your production environment will thank you for testing managed package deployments in sandbox first.

📚 Document Everything: Keep track of package versions and customizations. Your team (and future you) will appreciate the

Ready to Deploy?

With Copado Essentials, managed package deployment becomes a smooth, predictable process. Whether you're upgrading a single package or managing deployments across hundreds of orgs, you've got the tools and knowledge to do it right.

Remember: start simple, validate everything, and don't be afraid to leverage automation as you scale. Happy deploying!

Did this answer your question?