![salesforce ant migration tool retrieve custom fields salesforce ant migration tool retrieve custom fields](https://1.bp.blogspot.com/-PXdB8hopAOo/YFC18QWY5VI/AAAAAAAARLw/n7NcSlemLmscIeMqIgRIexj6eG7vBXIygCLcBGAsYHQ/s806/Custom%2BField%2Bin%2BChat%2BTranscript%2Bobject%2BSalesforce.jpg)
![salesforce ant migration tool retrieve custom fields salesforce ant migration tool retrieve custom fields](https://i.stack.imgur.com/t8KSw.png)
- #Salesforce ant migration tool retrieve custom fields how to
- #Salesforce ant migration tool retrieve custom fields software
This automation greatly frees up you and your team to work in the platform, make declarative and programmatic changes directly in your sandbox or production instance, and have peace of mind that behind the scenes all the metadata is being backed up to source control! Getting Setup
#Salesforce ant migration tool retrieve custom fields how to
That is a valid use case, but what I want to share with you is how to setup a very simple ant script to retrieve all the metadata from your Salesforce instance then commit the metadata to git source control so that you can begin scheduling routine backups of all your customizations. There are plenty of resources online about how to setup continuous integration with Salesforce, but those assume you are doing work in one org and wanting changes synced to other orgs.
#Salesforce ant migration tool retrieve custom fields software
So how do we apply the software development best practices of source control, or at least a versioned backup of our customizations, to the environment? The answer is the Migration Tool! And if you’re not careful, it’s also very easy for other developers to accidentally overwrite those customizations and no native way to rollback.
![salesforce ant migration tool retrieve custom fields salesforce ant migration tool retrieve custom fields](https://i.stack.imgur.com/bgXKl.png)
There is no commit to source code repository and there isn’t any deployment from your local machine into Salesforce. (if not, get started today!)īut after working on the platform for a while you quickly realize, as a cloud service, anytime you make an apex code change or workflow tweak or create a formula field, that change has occurred instantaneously to that Salesforce org. You maintain a backup of your code in the source code repository where you can version it and rollback to if necessary. If you’re coming to the platform with background as a traditional programmer then you’re likely accustomed to geeking out some code on your local machine then committing to a source control repository, such as git or cvs, then deploying to a server. But it also supports programmatic customizations too, such as apex classes, triggers, controllers, and visualforce pages. creating custom objects, fields, formulas, workflows, reports, etc.). With its declarative nature, many customizations require no code at all (e.g. Salesforce is a unique development environment.