This is the second post in a two-part series presenting how to work with Developer Sandboxes and the Salesforce CLI. Over the course of this series, we’ll cover:

* * Manage sandboxes with the Salesforce CLI
* Clone sandboxes instead of creating new ones
* Initialize sandboxes with a custom Apex class (Beta)
* Secure your production Org with sandbox-only users
* Import sample data
* Refresh outdated sandboxes
* Delete unused sandboxes

* PART 2: METADATA MANAGEMENT
* Prefer the source format over the metadata format
* Retrieve metadata with the Org Browser
* Retrieve metadata that do not support wildcards in package.xml (reports, dashboards…)
* Remove metadata that’s no longer needed
* Leverage Custom Metadata to pass configuration from Production to your Developer Sandbox
* Test metadata deployments

In this final part, we’ll focus on metadata management for Developer sandboxes, but these best practices can be expan…

Please click here to read the original article as posted on Salesforce Developers Blog.

We source the web to bring you best Salesforce articles for our reader’s convenience. If you want to have this article removed, please follow guidelines at Digital Millennium Copyright Act (DMCA)..

LEAVE A REPLY

Please enter your comment!
Please enter your name here