Sandboxes refreshed or newly sourced from a production org may contain metadata from an existing SpringCM integration. When this occurs, administrators may see the following error message when initially viewing SpringCM content.
Salesforce sandboxes are populated by copying the metadata from a source org. In the case of a new sandbox, the metadata will be sourced from a production org. Since the metadata is copied from an existing org, there are now two orgs seemingly pointed to the same SpringCM account. To remedy the error, the sandbox must be connected to a single, unique SpringCM account.
It is important to note that although the sandbox may appear connected to an existing production account, that is not the case. Making changes to the SpringCM setup in the sandbox org has no impact on the source production org.
Select the section which best fits your use case:
For newly sourced sandboxes, the issue can be resolved by simply deleting and re-connecting the SpringCM integration.
Delete the Existing Connection
- In Salesforce, select SpringCM from the drop-down menu:
- Click Delete Connection
- You will be prompted to enter your Salesforce Administrator credentials.
- An Allow Access? prompt will open. Click Allow.
- Upon redirect to SpringCM, you will need to login as a Super Administrator in the account.
- Upon entering valid credentials, the process will complete. You will see a Success! notification if the connection was deleted.
- Click Done to close the prompt and return to Salesforce setup.
If you encounter the error shown below after entering SpringCM credentials, check the SpringCM Address Book to ensure that you are authenticating with valid credentials from a Super Administrator in that environment. Close this warning and reattempt Step 5.
Setup a New Connection
- Return to the SpringCM Setup page within Salesforce (Step 1 above).
- Click Setup Connection
- Click the radio button for the SpringCM environment you want to integrate with your sandbox:
- Repeat Steps 3-7 from the previous section to complete the connection setup.
Upon completion, you should see the correct account, environment and org id shown under the connection details.
Still not resolved? We suggest moving on to the next section, which addresses sandbox orgs previously connected to another SpringCM environment.
Salesforce Administrators commonly repurpose or refresh sandboxes during the lifecycle of a project. As such, a sandbox org may have been previously connected to another account in a different SpringCM environment, resulting in conflicting environmental metadata.
Follow the steps below to remove any previously connected environments.
- In Salesforce, click Setup:
- In the left-hand navigation bar, under the Administer heading, select Manage Apps:
- Select Connected Apps and click the SpringCM FileIt hyperlink (not Edit):
- Scroll to the bottom of the page and click the Environment link:
- To the right of the Custom Setting Definition Detail header, click Manage:
- You should see more than two connected SpringCM environments listed. Click the Del button for all environments to which you do not wish to be connected:
- For each environment you delete, you will be presented with an Are you sure? pop-up. Click OK:
After all unwanted environments are removed, you should be able to see SpringCM File It content in Salesforce. Users may need to refresh their Salesforce browser window(s) if opened prior to any changes being made.