Troubleshooting (Salesforce)

In Oneflow, you will be given an API token. This token allows the Oneflow for Salesforce application to connect to Oneflow. Go to Marketplace in Oneflow to enable the Salesforce extension.

Cause: Oneflow for Salesforce API token is missing or no longer valid.

Solution: Make sure “Oneflow for Salesforce” is set up by navigating to the Marketplace in the Oneflow app (only visible to users with the Oneflow Administrator permission set) and following the steps shown in the “Get Started” guide.

For more information on setting up our application, follow the steps below. OR

Cause: Salesforce user's email does not match Oneflow user email.

Solution: Make sure the user has the same email on both systems.

Cause: Salesforce user email and Oneflow user email are different.

Solution: Ensure there is a registered Oneflow user with the same email address as the current Salesforce user seeing this error.

Cause: This error often occurs after upgrading the Oneflow package.

Solution: Go to Setup > Custom Settings > Oneflow Application Settings > Manage. Click Edit. Check the IsProductMappingEnabled checkbox and click Save.

Cause: At least two participants have the same email.

Solution: When creating a contract, make sure all emails shown in the participants list are different. Also, ensure that none of the participants uses the same email as the Salesforce user creating the contract.

Cause: At least two participants have the same phone number.

Solution: Ensure all phone numbers in the participants list are unique.

Cause: Country mapping is set to a field where the value is “Sweden” instead of the ISO country code “SE”.

Solution: Update the field value to use the ISO country code (e.g., SE) instead of the country name.

Cause: User profile is missing required permissions (often occurs for non-admin users).

Solution: Make sure the following permissions are granted to the user’s profile.

Administrative Permissions:
View All Data
View Setup and Configuration

General User Permissions:
Manage Flow

Overview
If you’re receiving a permission error when creating a contract after the latest package upgrade, it’s related to new security validations introduced in this release.

What Changed
As part of the recent upgrade, we’ve enforced CRUD (Create, Read, Update, Delete) and FLS (Field-Level Security) checks within Salesforce. This enhancement aligns with Salesforce’s security review standards and ensures stronger protection for data shared between Salesforce and Oneflow.

Why You’re Seeing This Error
With these checks in place, Salesforce now verifies whether users have the necessary object and field-level permissions before performing any data operation. If a user doesn’t have access to one or more fields configured for data synchronization between Salesforce and Oneflow, a permission error may appear — even if those fields aren’t directly displayed or used in the contract.

How to Fix the Issue
To resolve this:

• Identify all fields selected for data transfer or sync between Salesforce and Oneflow.
• Verify that the affected user or permission set has both Read and Edit access to these fields.
• Grant access even to fields not directly used in the contract, since the sync process may reference them during execution.

Example
If your setup syncs fields such as Account.Name, Opportunity.Amount, and Object__c.Field__c, ensure users have:

• Read access for all referenced fields.
• Edit access where updates are required for syncing.

Summary
This change improves data security and compliance with Salesforce standards. By updating field permissions for all synced fields, you can resolve the permission error and ensure smooth contract creation and synchronization between Salesforce and Oneflow.