Skip to Content

TheBlogReaders.com

Salesforce.com, PHP, MySQL, Javascript, Ajax, Htacces

Difference between Salesforce Changeset, Force.com IDE, Force.com Migration Tool

Be First!
by August 13, 2018 SALESFORCE

Difference between Salesforce Changeset, Force.com IDE, Force.com Migration Tool

Difference between Salesforce Changeset, Force.com IDE, Force.com Migration Tool

ChangeSet – https://help.salesforce.com/articleView?id=changesets.htm&type=5

Get Started with the Force.com IDE – https://developer.salesforce.com/docs/atlas.en-us.eclipse.meta/eclipse/ide_getting_started.htm

Ant Migration Tool – https://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/meta_development.htm

 

Salesforce Deployment Strategy Comparison Changeset vs Force.com IDE vs Force.com Migration Tool
Change set Force.com IDE Force.com Migration Tool
How-to use Use Setup > Deploy > Outbound / Inbound Changesets Use “Deploy to Server” in Force.com ide / Mavensmate and choose the components to deploy Use Ant scripts and Build.xml to specify what elements are to be retrieved / deployed
When to use When minor changes are to be manually deployed between Sandbox and other Sandbox or production.
When there are lot of dependencies, its easy to use Changeset to easily add all dependencies in single click
Manual Deployment between different Salesforce orgs which may or maynot be connected All of Force.com IDE capability PLUS
Automate deployments by executing scripts in tools like Jenkins, Hudson
Fetch code from (Source control, Salesforce Org, File system) and perform script action etc.,
Detailed differences
1 No need of destination credentails to push changes Credentials for destination necessary Credentials for destination necessary
2 History of deployments maintained for each deployment No history of deployment maininted No history of deployment maininted
3 FLS can’t be deployed in Changeset Profile along with FLS is deployable Profile along with FLS is deployable
4 Dependency can be easily added (in single click) All dependencies should be manually added All dependencies should be manually added
5 Every source needs individual changeset to deploy to its destination Deploy to server – you need to choose the list of changes to deploy everytime Use the existing xml configuration (for deploying file list) and can be reused in different (build.xml) target configuration
6 Always latest code changes can be deployed Always latest code changes can be deployed but latest code changes are fetched from file system so source can differ from the Org Can deploy in multiple ways – Fetch specific source control version to deploy, use filesystem to deploy or from Salesforce Org.
Also have to specify on the API version for deployment by types (Class, Pages, etc.,)
7 Suitable for medium sized teams using connected orgs Suitable for small teams (Ex – Dev org to Sandbox orgs connected / Disconnected orgs Suitable for Large teams with Continuous deployment from SCM

Unsupported Salesforce Metadata Types:-

The following components can’t be retrieved or deployed with Metadata API, and changes to them must be made manually in each of your organizations:

  • Account Teams
  • Activity Button Overrides
  • Analytic Settings
  • Auto-number on Customizable Standard Fields
  • Campaign Influences
  • Case Contact Roles
  • Case Feed Layouts
  • Case Team Roles
  • Console Layouts
  • Currency Exchange Rates
  • Data Category Visibility Settings
  • Delegated Administration
  • Divisions
  • Email Services
  • Fiscal Year
  • HTML Document and Attachment Settings
  • Lead Settings
  • Mail Merge Templates
  • Mobile Administration
  • Mobile Users and Devices
  • Offline Briefcase Configurations
  • Opportunity Big Deal Alerts
  • Opportunity Update Reminders
  • Organization Wide Email Addresses
  • Partner Management
  • The following standard picklists: Lead.CampaignMemberStatus, Opportunity.ForecastCategoryName, and Order.Status. (All other standard picklists are supported.)
  • Predefined Case Teams
  • Product Schedule Setup
  • Public and Resource Calendars
  • Quote Templates
  • Salesforce to Salesforce
  • Standard fields that aren’t customizable, such as autonumber fields or system fields
  • Search Settings
  • Self-Service Portal Font and Colors
  • Self-Service Portal Settings
  • Self-Service Portal Users
  • Self-Service Public Solutions
  • Self-Service Web-to-Case
  • Site.com
  • Social Account/Contact Settings
  • Solution Categories
  • Solution Settings
  • Tag Settings
  • Territory Assignment Rules
  • User Interface Settings (except calendar features, which are supported in ActivitiesSettings)
  • Web Links on Person Account Page Layouts
  • Web-to-Lead

(3)

Previous
Next

Leave a Reply