Overview
The Salesforce connector provides a wide variety of customization and extension options. While this gives you more flexibility in configuring the Salesforce integration to better fit your business processes, certain configurations may create functional issues for the integration and its performance (e.g. reaching a bulk sync limit that is implemented by Salesforce).
In this article, you’ll learn more about the most common issues and their potential impacts, as well as any workarounds that may be available. It’s recommended to revisit this article for any future updates as additional issues and their corresponding solutions are discovered.
Support for Extension Points and Customizations
Extension points allow you to extend or override the Salesforce connector’s core functionality with custom solutions using Apex code. Support for extension points and other customization options—such as Flows, Apex classes and triggers, process builders, and non-Kantata integrations—is limited. Due to these limits, it’s recommended to evaluate any recent changes in Flows, scale in organizations, or processing volumes prior to contacting the Kantata OX Support team when you experience an issue.
Supported Salesforce Connector Versions and Settings
The most current Salesforce connector version is 2.11. We recommend upgrading to this version to benefit from the new features and improved performance it offers. For more information, please see the Salesforce Integration Version 2.11 Release Notes article.
All connector versions earlier than 2.8 are no longer supported by our team outside of basic troubleshooting and general inquiries. Additionally, the legacy configuration settings listed below are no longer supported for versions 2.8 and higher. Continuing to use these legacy features may lead to performance issues, security vulnerabilities, and less compatibility with newer updates:
- Nonstandard OLI
- Nonstandard OLI Ref Field
- Nonstandard Price Field
- Nonstandard Currency Field
- Enable Legacy Time Entry Processing
- Enable Legacy Expense Processing
Known Salesforce Connector Issues
| Issue | Description | Solution | Status |
|---|---|---|---|
|
SOQL queries limit is reached (Error message: Too Many SOQL Queries).
|
The number of SOQL queries in a sync exceeds the Salesforce limit, causing the integration to fail.
|
Temporarily deactivate the Enable Opportunity Processing Salesforce setting.
|
This issue has improved with the 2.11 connector.
|
|
Projects are unintentionally duplicating.
|
Rapid updates in Salesforce triggered multiple jobs, causing the project to duplicate in Kantata OX. |
N/A
|
This issue is currently being investigated by our team. |
|
Asynchronous future jobs limit is reached (Error message: Too Many Future Calls).
|
The number of asynchronous Apex jobs made in a sync (or in quick succession) exceeds the Salesforce limit. Salesforce enforces this limit on all integrations—not just the Kantata OX integration—and is account-wide. |
N/A
|
A new feature request has been logged.
|
|
Opportunity Line Item project stage and fields aren't syncing.
|
The Kantata OX project status and mappings are out of sync with the Opportunity stage if the Kantata OX project is created via an Opportunity Line Item. | Update the Kantata OX project Object (e.g. a description field), which triggers an update that syncs back to the Opportunity. |
This issue has improved with the 2.11 connector.
|
|
Queued jobs limit is reached.
|
The number of queued jobs that can be performed at the same time exceeds the Salesforce limit of 50. |
N/A
|
This issue has improved with the 2.11 connector.
|
|
Salesforce connector volume limit reached (Error messages: APEX LIMIT / APEX CPU LIMIT / APEX HEAP LIMIT). |
There is a high volume of Objects—such as tasks, time entries, and expenses—that the Salesforce connector is trying to sync at the same time.
|
N/A
|
A new feature request has been logged.
|
Comments
0 comments
Please sign in to leave a comment.