Skip to main content
Back to Kantata.com Blog Tour Status

Salesforce Integration Version 2.11 Release Notes

By Jennifer Goodsell | Updated

Installation

The Salesforce integration version 2.11 can be installed as a new installation or as an upgrade to an older version. For current Salesforce integration users, please contact our Support team to upgrade your existing integration.

Please note that our Support team will only provide the installation link and the steps to install the 2.11 version. If you wish to be advised or consulted on any new features or functions, please contact Customer Success.

Note: Please check for customizations and/or extension packages before upgrading to 2.11. It’s also recommended to test the upgrade in a Salesforce sandbox environment to confirm functionality and compatibility with your organization's processes and architecture.

Release Highlights

The version 2.11 of the Salesforce integration includes the following enhancements:

  • Support for Project Estimate Stage from Opportunities and Opportunity Line Items
  • Support for Project Status on Opportunity Line Items (Updated)
  • Support for Project Budget via Custom Field from Opportunities and Opportunity Line Items 
  • Support for Time Adjustments 
  • Support for Project Colors 
  • Synchronization Status Panel
  • 2.8 Upgrade Configuration Fix (Updated)
  • Staging Table to Sync Objects

Support for Project Estimate Stage from Opportunities and Opportunity Line Items

Delivery projects can now sync the Project Stage to and from Kantata OX. The Estimate Stage data point is now available on the Custom Project Object within Salesforce for delivery projects. This new choice field shows the current project stage—either Project or Estimate— from Kantata OX. It can be changed in Salesforce and then synced to Kantata OX. If desired, clients can also use a custom process to automate updating the stage in Salesforce (e.g. setting project stage based on opportunity progress). Services, partners, or your Salesforce administrator can be engaged to assist. Please contact Customer Success for more details.

Note: Only Delivery projects are supported by this feature; Business Development projects are not supported at this time.
Note: The Estimate Stage Projects feature is separate from the Kantata OX legacy Estimates feature. This enhancement specifically adds support for Estimate Stage projects.

Support for Project Status on Opportunity Line Items

Projects created by Opportunity Line Items (OLI) now update and sync their respective project statuses based on the stage of the Opportunity. Previously, the OLI project status would only sync at the time of creation and no further updates would sync. This enhancement now makes the OLI status behavior consistent with the established Opportunity behavior.

Support for Project Budget via Custom Field from Opportunities and Opportunity Line Items

The Kantata OX project budget can be set via custom fields on the Opportunity or Opportunity Line Item. Projects created via an Opportunity must use an Opportunity custom field and projects created via an Opportunity Line Item must use an OLI custom field. Each field type must be either number or currency.

Support for Time Adjustments

Time adjustment records, which are different from time entries, can now sync from Kantata OX to Salesforce for creates, updates, and deletes. This feature is controlled by the new configuration option Show Time Adjustments, available on the Integration Options tab on the Configuration page.

This feature utilizes the new subscribed events API architecture. It separates Time Adjustments from the standard integration sync process, increasing the efficiency of the integration while reducing the likelihood of hitting Salesforce’s governor limits. Time adjustments will sync automatically on schedule in the background but can also be synced on demand. Additionally, backdating functionality has been added for Time Adjustments in case the desired subscribed event has expired (typically after 9 days).

Support for Project Colors

The integration now supports syncing Project Colors. Project colors can be set or changed in Salesforce—which sets or updates the project color in Kantata OX—via a new Project Color custom field drop-down in the project Object.

Note: Additional setup is required to utilize this feature. To learn more, see the Adding Project Colors in Salesforce Knowledge Base article.

Synchronization Status Panel

A new Synchronization Status Panel has been added to the Salesforce integration’s homepage. This panel shows when the integration last synced time and Time Adjustments (if enabled). You can click the Sync Projects button on the panel to sync the integration on demand. Objects using the new subscribed events architecture can also be synced automatically by clicking the Sync Time Adjustments button. Please note that this process may take some time depending on the amount of changes and data to sync. If the staging table is enabled, processing data and timestamps for the table also displays in the panel.

2.8 Upgrade Configuration Fix

Previously, when upgrading to Salesforce version 2.8, there was an added option that required an input. If no input was given, the configuration page could not be saved. This is now resolved and you can now upgrade to 2.11 without any configuration changes while preserving the existing configuration.

Staging Table to Sync Objects

A new opt-in staging table has been added to assist with the processing of all integration-related objects. Previously, especially when syncing large amounts of data from Kantata into Salesforce, the integration could encounter several different errors and fail to process the whole amount of data. Some of the error messages included:

  • Heap size too large
  • Too Many SOQL Queries
  • Apex CPU time limit exceeded

In other words, the amount of data was so large, the integration was running into the governor limits that the Salesforce platform has in place. This staging table allows the integration to process high volume data with significantly increased efficiency, reducing the occurrence of these errors, and corrects the issue of duplicate projects being created due to the CPQ Salesforce feature being activated.