Salesforce

First, we are going to see the issues experienced in Salesforce when establishing the connection with SaaSify. We have divided this into four sub-sections: 

1. External Credentials

2. Named Credentials

3. Principal Access

4. Tenant-Level permissions

External Credentials

There are three common issues that we might come across in the External Credentials in Salesforce. Below are the following issues and solutions to them: 

Problem 1: Incorrect Name 

You will come across the following error “Field SaaSify_API_Credential.UserName does not exist. Check spelling.” when testing the connection. 

Solution: We need to ensure that we are providing the following value in the Name field SaaSify_API_Credential in the External Credentials section. 

Problem 2: Misspelled of UserName in the Authentication Parameters section 

You will come across the following error “Field SaaSify_API_Credential.UserName does not exist. Check spelling.” when testing the connection. 

Solution: To correct this issue, we need to ensure that, U and N are in Uppercase in UserName. 

Problem 3: Incorrect Password/UserName 

You will face the following error “401-Unauthorized” when testing the connection. 

Solution: To fix this problem, we need to make sure that we are providing the right UserName/Password under Authentication Parameters. The values for UserName and Password will be provided by the SaaSify team.

Named Credentials

There are 3 common issues that we might come across in the Named Credentials in Salesforce.

Below are the following issues and solutions to them:

Problem 1: Incorrect Name

You will come across the following error “The callout couldn't access the endpoint. You might not have the required permissions, or the named credential "SaaSify_API_Connection" might not exist.” when testing the connection.

Solution: To fix this problem, ensure that you are providing the following value SaaSify_API_Connection in the Name field under Named Credentials.

Problem 2: Entered URL is incorrect

You will come across the following error “401-Unauthorized” when testing the connection.

Solution: To fix this problem, we need to make sure that, we are checking with the SaaSify team and entering the right value for the URL. The value for URL will be provided by the SaaSify team.

Problem 3: Callouts are disabled

You will face the following error “Callout blocked for named credential. Be sure the Enabled for Callouts setting is enabled to allow usage of this credential.” when testing the connection.

Solution: To fix this problem, we need to make sure that Enabled for Callouts is enabled.

Principal Access

We need to be sure that we are enabling the External Credential Principal Access for the System Administrator Profile for the connection between Salesforce and SaaSify to be successful. If this is not enabled, then we will face the below problem:

Problem: When Principal Access is not provided to System Administrator Profile

You will face the following error “We couldn't access the credential(s). You might not have the required permissions, or the external credential "SaaSify_API_Credential" might not exist.” when testing the connection.

Solution: To correct this issue, we need to make sure that, we are enabling the External Credential Principal Access for the System Administrator Profile by following the below steps:

1. Navigate to Setup (Gear icon) and select Setup from the drop down

2. Search for Profiles under Quick Find and click on it

3. Click the Profile labeled “System Administrator”

4. Click on “External Credential Principal Access” within the System Administrator Profile

5. Click on Edit

6. Under Available External Credential Principals, select “SaaSify_API_Credential – Credentials”.

7. Select "Add" to include it in the list of Enabled External Credential Principals.

8. Click Save.

Tenant-Level Permissions in SaaSify (Done by the SaaSify Team)

The Tenant-Level permissions are required to publish the Private Offers, Co-sells, CPPO from the Salesforce. This will be done by our SaaSify Engineering team from the backend. If this is not enabled, then you will come across the below issue:

Problem: Tenant-Level Permissions needs to be enabled in SaaSify

If the Tenant-Level permissions are not enabled then, you will face the following error “Bad Request, Private Offer creation denied” when publishing the Private Offer in Salesforce. You can receive a similar error when trying to publish Co-sells, CPPO.

Solution: If you can come across this issue, then please reach out to your Partner Success Manager or email us: psm-saasify@spektrasystems.com. You can also reach out to our SaaSify Support Team on saasify-support@spektrasystems.com and provide the error details with the screenshot to get this issue resolved.