App Config: Full and Partial Sandboxes are throwing errors or are not allowing Users access to modules etc.

Issue:

Clients who create Dev, Partial or Full Copy and UAT Sandboxes copied from Production environments may find that ClosePlan throws errors regarding access to modules.

Error Messages:

  • “Metadata API not configured.”

  • “Sales Process cannot be validated due to disabled access to Metadata APIs”

In order to configure Object Picklists for Relationship Maps, set up Sales Processes for Playbooks, Metadata API access must be provided

 

Solution:

  • Check to see if Metadata APIs are configured.

    • Go to ClosePlan Admin Tab > Environment > Relationships > Picklist Values..

If you don't see the Picklist Values, that is an indicator that one or all of the following are happening:

  • URLs are not correct in configuration

  • Consumer Secret and/or Consumer Key information are not updated

  • Named Credentials are not authorized correctly or are authorized by an inactive user.

If this is a copy of a Production for example, the after-Install configuration needs to be updated (copies point to old info from the original)

Normally, following the instructions here will resolve the issue:

Sandbox Refreshes

 

1. Check Connected App:

Check/correct the URL

  • if you need to correct the URL, then the connected app will generate a new keys and you will need to change the keys in step 2 and update step 3

 

2. Auth Provider

Check the Consumer Key and Secret and replace if needed or in doubt.

 

3. Named Credentials

Check/correct the URL and then reconfirm the named Credentials by saving

After you click on Save, you will be redirected to log in. Log in with the correct Credentials for the correct Sandbox.

If you are not directed to log in to Salesforce, wait 5 minutes then:

Setup > Named Credentials > Click ‘Edit’ next to ClosePlan Metadata Service and Save.


NOTE:

Confirm the Named Credentials used are from the correct Org!

(Users see the Metadata API error when Sandbox Named Credentials are confirmed with an incorrect User ID, for example a Production Org log in.)