---
title: "Salesforce"
slug: "salesforce"
updated: 2025-07-18T11:09:24Z
published: 2025-07-18T11:09:24Z
canonical: "docs.saasify.ai/salesforce"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.saasify.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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
5. Custom Metadata Types
6. Package Installation Failure

## 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/ 404-Not Found**” 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](mailto:psm-saasify@spektrasystems.com). You can also reach out to our SaaSify Support Team on [saasify-support@spektrasystems.com](mailto:saasify-support@spektrasystems.com) and provide the error details with the screenshot to get this issue resolved.

## Custom Metadata Types

We need to ensure that the endpoint is correctly updated under Custom Metadata in Salesforce.

**Problem:** When accessing the EULA in Salesforce, you might encounter the following error "**An error occurred while processing the request. Please contact support for further assistance.**" This issue typically occurs when the **endpoint** value under **Custom Metadata** is not correctly set.

**Solution:** To resolve this issue, ensure that the endpoint is properly configured in Salesforce by following these steps:

1. Click on the **Gear icon** (top right) and select **Setup**.
2. Under **Quick Find**, search for **Custom Metadata Types** and click on it.
3. Locate and open **SaaSify Setting**, then click on **Manage Records**.
4. Update the **Setting Value** based on your SaaSify web app environment configured in Salesforce:
5. For Production environment: **https://api.saasify.ai**
6. For Portal environment: **https://api-portal.saasify.ai**

Make sure the correct URL is updated to prevent EULA processing errors.

## Package Installation Failure

**Problem:** If you're facing a package installation failure error, such as: **"Your request to install package 'SaaSify ver 3.120' was unsuccessful. None of the data or setup information in your salesforce.com organization was affected."**

**Solution:** Please enable the following settings in Salesforce:

- **Content Deliveries feature can be enabled for users**
- **Public Links can be enabled for users** (this requires Content Deliveries to be enabled)

**Steps to Enable:**

1. Click the **Gear** icon (top right) and select **Setup**.
2. In the **Quick Find** search bar, type **Content Deliveries and Public Links** and click on it.
3. Enable the following two options:
  - *Content Deliveries feature can be enabled for users*
  - *Public Links can be enabled for users (Requires Content Deliveries)*
4. Click **Save**.

**Note:** If they are not able to see these features, please ask them to create a ticket with the Salesforce team, they can enable this feature [https://help.salesforce.com/s/articleView?id=000383532&type=1](https://help.salesforce.com/s/articleView?id=000383532&type=1)

Once these settings are enabled, please retry the package installation.

**QA1:** Why SaaSify needs Content Delivery and Public Links feature?

**Answer:** When we create Private Offer for AWS | GCP | MS we have option to upload the files (Customer Terms), These files needs to be shared outside of SF so that SaaSify can use this file to create Private Offers

**QA2:** Content Delivery and Public Links is this feature is supported in classic or lightning or Both?

**Answer:** Official document state this is available in classic [https://help.salesforce.com/s/articleView?id=sf.lex_gaps_limitations_files_and_content.htm&type=5](https://help.salesforce.com/s/articleView?id=sf.lex_gaps_limitations_files_and_content.htm&type=5), However this is also supported in Lightning.

**QA3:** Enabling this feature SaaSify gains access to what in Salesforce?

**Answer:** We have access to files which was uploaded during Private offer creation.