{"id":1156,"date":"2015-07-30T06:50:16","date_gmt":"2015-07-30T06:50:16","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/salesforce\/?p=1156"},"modified":"2025-06-20T09:10:51","modified_gmt":"2025-06-20T09:10:51","slug":"different-deployment-methods-in-salesforce","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/salesforce\/2015\/07\/30\/different-deployment-methods-in-salesforce\/","title":{"rendered":"Different Deployment Methods in Salesforce"},"content":{"rendered":"

Salesforce Deployment is nothing but copying\/transferring Salesforce metadata from one Salesforce organization to another.\u00a0There are various methods to achieve Salesforce metadata deployment.<\/p>\n

Different Deployment Methods<\/strong><\/span><\/p>\n

    \n
  1. Change Sets<\/li>\n
  2. Eclipse with Force.com IDE ( Deprecated)<\/li>\n
  3. Force.com Migration Tool \u2013 ANT\/Java based<\/li>\n
  4. Salesforce Package<\/li>\n
  5. VSCode Salesforce Extension Pack<\/a><\/li>\n
  6. Salesforce Code Builder <\/a><\/li>\n<\/ol>\n

    Change Sets<\/strong><\/span><\/p>\n

    The easiest way to send configuration changes from one Salesforce organization to another is to use a change set though it has a limitation that we can use it among connected Salesforce orgs only (like Developer Sandbox to Test Sandbox & Test Sandbox to Production Org etc). We cannot use it in between any individual Salesforce orgs.<\/p>\n

    To use change sets we need to have two Salesforce org’s i.e. one Production org and its Sandbox org.<\/p>\n

    Production Org:<\/span><\/strong>
    \nIt is Salesforce org with live data which is being actively used.<\/p>\n

    Sandbox:<\/span><\/strong>
    \nA sandbox is a copy of your production organization. Sandboxes contain the same metadata as production organization.<\/p>\n

    Outbound Change Sets:<\/span><\/strong>
    \nMake changes in the organization you are logged into, and upload those changes to another organization.<\/p>\n

    Inbound Change Sets:<\/span><\/strong><\/p>\n

      \n
    1. Accept, modify, or reject change sets uploaded from other organizations.<\/li>\n
    2. Change sets require a deployment connection between the two Salesforce organizations.<\/li>\n
    3. The first step is to create this connection. To create a connection, follow the below steps:<\/li>\n<\/ol>\n

      Steps to create Deployment Connections<\/strong><\/span><\/p>\n

        \n
      1. Create one or more sandboxes.<\/li>\n
      2. Go to Setup >> App Setup >> Deploy >> Deployment Connections \/ Deployment Settings. It will show you information on Change set and Outbound\/Inbound change set information. Press \u2018Continue\u2019 button on this page.<\/li>\n
      3. Click \u2018Name\u2019 to view existing connection details. We can see this record only if Sandbox is created for Production Org.<\/li>\n<\/ol>\n

        \"Deploy<\/a><\/p>\n

          \n
        1. Click \u2018Edit\u2019 to authorize inbound changes from a listed organization.\"Deploy<\/a><\/li>\n<\/ol>\n

          Steps to create Outbound Change Sets<\/span><\/strong><\/p>\n

            \n
          1. \n
              \n
            1. In a related sandbox org, use Deployment Connections to authorize inbound changes from this production org (same as shown in above screenshot).<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
                \n
              1. Go to Setup >> App Setup >> Deploy >> Outbound Change Sets.<\/li>\n
              2. Click on \u2018New\u2019 to create a new Change Set.<\/li>\n<\/ol>\n

                \"Deploy<\/a><\/p>\n

                  \n
                1. Click \u2018Add\u2019 to include Salesforce components in your changeset.<\/li>\n<\/ol>\n

                  \"Deploy<\/a><\/p>\n

                  This displays a list of all Salesforce components like Apex Classes, Packages, Tabs etc. You can choose the type of component and the components you want to add, and then click Add to Change Set.<\/p>\n

                  \"Deploy<\/a><\/p>\n

                    \n
                  1. Click \u2018Add Profiles\u2019 to add profile settings to the change set.\"Deploy<\/a><\/li>\n
                  2. Click \u2018View\/Add Dependencies\u2019 to add dependent components.
                    \nDependent components rely on the existence of other components. Unless you are certain that the dependent components exist in every organization this change set will be deployed to, it’s a good idea to add dependent components to the change set.
                    \n                    \"Deploy<\/a><\/li>\n
                  3. Click <\/span>\u2018Upload\u2019<\/b><\/span> to send these components to another org. <\/span>Select the organization you want to send the change set to and then click \u2018Upload\u2019<\/b><\/span>.\"Deploy<\/a>\u00a0<\/strong><\/li>\n<\/ol>\n

                    Steps to create Inbound Change Sets<\/span><\/strong><\/p>\n

                      \n
                    1. Log into an org that has received a changeset i.e. Sandbox Org.<\/li>\n
                    2. Go to Setup >> App Setup >> Deploy >> Inbound Change Sets.<\/li>\n
                    3. Click a change set name to see its detail.<\/li>\n
                    4. Click \u2018Validate\u2019 to validate a changeset without deploying changes. Validating a changeset allows you to view the success or failure messages you would receive with an actual deploy.It is highly recommended to validate Change sets before deploying it.
                      \nThis is a good idea if you are planning a deployment in future and want to determine if the deployment will succeed ahead of time.<\/li>\n
                    5. Click \u2018Deploy\u2019 to apply the change set to your Org.<\/li>\n
                    6. Once the deployment completes, click \u2018View Results\u2019 to see the status and individual changes or errors.<\/li>\n<\/ol>\n

                      Deployment Status<\/strong><\/span><\/p>\n

                      You can monitor deployments that are in progress, check which deployments are waiting for execution, and view the results of completed deployments on the Deployment Status page. To track the status of deployments, click Setup >> App Setup >> Deploy >> Deployment Status. Deployments are listed in different sections depending on their status.<\/p>\n

                      This is how we can deploy metadata using Change Sets. In our next blog, we will discuss another method of deployment i.e. deployment using Eclipse with Force.com IDE.<\/p>\n

                      About Us<\/strong><\/span>
                      \n                      Greytrix<\/a>\u00a0as a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners across the globe. We offers Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that requires apex code incorporation into the Salesforce platform.<\/p>\n

                      Greytrix<\/a>\u00a0has some unique solutions for Cloud CRM such as Salesforce integration with\u00a0Sage Enterprise Management (Sage X3<\/a>),\u00a0Sage Intacct, Sage 100\u00a0<\/a>and\u00a0Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM\u00a0Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development<\/a> and Technical Support<\/a> to business partners and end users.<\/p>\n

                      Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n

                      For more information, please contact us at\u00a0salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n

                      Related Posts<\/strong><\/p>\n