Quick post today. Let’s differentiate between a Sandbox instance of Salesforce and a developer instance.
A sandbox instance is an exact copy of your Salesforce instance. It contains all the same metadata (such as workflows, custom fields/objects etc.) and, depending on the sandbox it can contain even your data (opportunities/accounts etc.). Depending on the edition of Salesforce you have, these can be costly to have. There are four different type of sandboxes:
- Developer – Includes all metadata, configuration and users. 200MB storage limit. No data is transferred to this sandbox. Can be refreshed once every 24 hours.
- Developer Pro – Includes all metadata, configuration and users. 1GB storage limit. No data is transferred to this sandbox. Can be refreshed once every 24 hours.
- Partial Copy – Includes all metadata, configuration and users. 5GB storage limit. A sample set of your data is transferred to this sandbox. Can be refreshed once every 5 days.
- Full Copy – This is a replica of your production bringing over all data and metadata. It has the same storage limit as your production instance. Can be refreshed once every 29 days.
All of these can be accessed by logging in through test.salesforce.com
A developer instance is fresh new environment with very limited storage. Unfortunately, you can’t copy any configuration or data into it but you can customise it to match your instance. If it doesn’t sound good then maybe the fact that it is FREE will change your mind. With a little bit of time and setup you can use this instance as you wish.
If you wish to create a developer instance go to https://developer.salesforce.com/signup and fill out the form.
Developer instances are accessed by logging in through login.salesforce.com
Also just wanted to mention ‘My Domain’ and why it has become more important. My Domain changes the domain of your Salesforce org from, for example, “https://ap4.salesforce.com” to “https://coroma.my.salesforce”. This grants several benefits to your organisation including branding your login screen and allowing several login security measures to be activated. It is also a requirement if you wish to enable Single Sign-On (http://coroma.com.au/setting-up-single-sign-on-with-azure-ad/), Social Sign-On (such as using a Google or Facebook account) and deploying Lightning Components within your instance.
And that’s a wrap. I did say it was a quick post. Thanks for reading!