Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More
Sandboxes: Staging Environments for Customizing and Testing
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Servers and IDs

            You are here:

            1. Salesforce Help
            2. Docs
            3. Sandboxes: Staging Environments for Customizing and Testing

            Servers and IDs

            Sandbox and production orgs have unique org IDs. The sandbox copy engine creates an org as part of each creation and refresh request.

            Required Editions

            Available in: both Salesforce Classic and Lightning Experience
            Available in: Professional, Enterprise, Performance, Unlimited, and Database.com Editions
            User Permissions Needed
            To view a sandbox: View Setup and Configuration
            To create, refresh, activate, and delete a sandbox: Manage Dev Sandboxes (Developer or Developer Pro only) or Manage Sandboxes (all sandbox types)
            • The org ID of the sandbox changes each time it’s refreshed. In any place where a production org ID or a sandbox org ID is used, such as text values and metadata, Salesforce inserts the new sandbox org ID value.

              To find the ID of the org that you’re logged in to, from Setup, enter Company Information in the Quick Find box, then select Company Information. A script or process, such as a test script or Web-to-Lead, that depends on a “hard-coded” org ID must use the current ID for the sandbox. When you deploy your changes to a production org, update the scripts or processes with the production org ID.

            • Salesforce creates sandbox orgs on several instances. When a sandbox is created or refreshed, Salesforce selects an instance for your sandbox. Sometimes, sandboxes appear on different instances and have different URLs.
            • When data is copied to a sandbox, object IDs for records are copied. Object IDs are unique identifiers for all objects—the same as the ID Field Type in the developer API. After being copied, however, object IDs don’t synchronize between the production org and sandbox. The sandbox and its corresponding production org act as independent orgs. Object data (and corresponding object IDs) that are created in the production org after the sandbox is created or refreshed don’t synchronize into the sandbox. The sandbox has the same behavior—new objects that are created in the sandbox aren’t synchronized back to the production org.
             
            Loading
            Salesforce Help | Article