Salesforce Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector For Salesforce for more information.
Version 1.6.0
Released June 15, 2021.
New And Noteworthy
- Support for Salesforce API versions 37 through 51. (SCSF-337, SCSF-103, SCSF-445)Note: To access the latest version of the Salesforce API you must modify the version number displayed in the Salesforce URL in the Connection dialog and then reset metadata for that Connection. For example, if your Salesforce URL is set to this https://login.salesforce.com/services/Soap/u/37.0 modify it to this https://login.salesforce.com/services/Soap/u/51.0. All new Salesforce Connections default to the latest supported version of the Salesforce API.
- Added Send operation functionality which is used to make API Calls to the Salesforce API. Send operation supports the Request entity used to build the HTTP call to the API. (SCSF-600, SCSF-536)
-
Added support for OAuth Connections including Single Sign-on and Multi-factor authentication. (SCSF-523)
Closed Issues
SCSF-405
When zero records are returned in the Salesforce Query Block, the Blocks inside the For Each Result Block still run. If custom error handling is enabled, an error is generated indicating that 0 records were returned. (Case # 01918900)
SCSF-403
Querying the AccountUserTerritory2View entity fails due to a malformed query. (Case # 01901968)
SCSF-401
Salesforceorganizations with the Kimble application installed sometimes cause the TIBCO Cloud™ Integration - ConnectSalesforce Connection to timeout when attempting to load metadata due to the large number of additional objects. (Case # 01884912)
SCSF-400
Message flows that use the Salesforce Bulk API and have Batch Processing enabled on target operation blocks sometimes generate errors similar to the following: (Case # 01871958)
Message: There was a problem accessing the Bulk API. Verify that the Bulk API was enabled for this account in Salesforce. The remote server returned an error: (400) Bad Request.
SCSF-395
Sometimes when attempting to retrieve object details for complex metadata, the metadata does not load and timeouts occur with errors similar to the following: (Case # 01864892)
A fatal error has occurred in the Salesforce Connector: The request channel timed out while waiting for a reply
SCSF-381
Querying ContentDocument and ContentVersion entities fails due to a malformed query. (Case # 01849609)
SCSF-27
When testing a Native Query in a flow, if the source datastore does not return any data, TIBCO Scribe® Online cannot build the schema for the underlying metadata and the flow cannot be saved.
SCSF-14
Using Like or Not Like operators with an empty string as Match Criteria generates errors similar to the following:
A fatal error has occurred in the Salesforce Connector: INVALID_QUERY_FILTER_OPERATOR:
(Account.Type != '')) AND ((NOT Account.Industry LIKE '')))
Known Issues
SCSF-632
Summary:In Debug mode, using a Native Query to return source data with a Fetch block that contains a For Each Child block generates errors similar to the following: (Case # 02066010)
The data is invalid.
Workaround: Instead of using a For Each Child block to retrieve a child entity, use another Fetch block to retrieve the required child entity.
SCSF-84
Summary: Data replication apps generate errors when attempting to replicate entities with relationships to other objects using externalid fields.
Workaround: Contact Support for Hotfix SCSF-84.
Version 1.5.1
Released May 5, 2020.
New And Noteworthy
- Support for Salesforce API versions 37 through 47. (SCSF-337, SCSF-103)Note: To access the latest version of the Salesforce API you must modify the version number displayed in the Salesforce URL in the Connection dialog and then reset metadata for that Connection. For example, if your Salesforce URL is set to this https://login.salesforce.com/services/Soap/u/37.0 modify it to this https://login.salesforce.com/services/Soap/u/47.0. All new Salesforce Connections default to the latest supported version of the Salesforce API.
- Added the ScribeExternalIdFieldName virtual field used when mapping external IDs in the Upsert Block to indicate which external ID to use for record matching. (SCSF-111)
- Added a Query Page Size field to the Connection dialog where you can specify the number of query results to return per page, between 200 and 2000. (SCSF-110)
Changes In Functionality
SCSF-23 / 68464
When a group of changes was written to Salesforce all at the same time, only a portion of them were returned by a subsequent query if the Salesforce datetimestamp did not include milliseconds. When a subsequent Data replication app executed and used Net Change to filter for new and updated records, some records were not included in the replication. (Case # 1727993, 66502)
For example, assume the last record written before the Data replication app completes had a modifiedon date of 09/04/2018 10:10:20 and the next Data replication starts with data that has a modifiedon date of 09/04/2018 10:10:21. Any records that arrived between the end of the Data replication app and 09/04/2018 10:10:21 were not included because milliseconds were not used as part of the filter.
To ensure that all records are replicated, the Connector subtracts one second from the most recent Last Modified Date, which could cause a small number of records to be reprocessed.
For example, if the last record written had a Last Modified Date of 09/04/2018 10:10:20, the next Replication starts with data that has a Last Modified Date of 09/04/2018 10:10:19. Any records that were already processed between 09/04/2018 10:10:19 and 09/04/2018 10:10:20 are processed again.
Closed Issues
SCSF-382 / SCSF 383
The Salesforce Connector was logging out of the Salesforce API after running a app, which caused other apps using the same Connection to fail with errors similar to the following: (Case # 01857906, 01857963, 01857932, 01857923, 01857970, 01857896, 01858068)
INVALID_SESSION_ID: Invalid Session ID found in SessionHeader:
If the Bulk API was used, errors similar to the following were generated: (Case # 01857932, 01857923)
There was a problem accessing the Bulk API. The remote server returned an error (400) Bad Request
SCSF-282
The Salesforce Connector was not checking the size of the batch files sent to Salesforce for processing, which was causing time out errors. To prevent timeouts the Connector uses the following limits to control the batch size: (Case # 1814857)
- Maximum of 10,000 records per batch
- Maximum of 10,000,000 total characters for all of the data in a batch
- Maximum of 10MB of data per batch
When any one of these limits is reached, the group of records is considered a complete batch and is sent to Salesforce for processing.
SCSF-106
The Salesforce Connector did not support the EmailMessage entity JunctionIdList data type fields used to specify RelationId values that control the From, To, CC, and BCC values of an email.
SCSF-105
Using the Salesforce Bulk API to retrieve and replicate large sets of data sometimes failed and generated errors similar to the following:
An existing connection was forcibly closed by the remote host.
SCSF-99
Filtering queries for the ContentDocumentLink entity generated Malformed Query errors. (Case # 01761221)
SCSF-31
Testing a Native Query never completed when using a Salesforce Native Query Block that contained one or more Regular Expressions. Instead, the process displayed a Please Wait message, failed to compile the query, and never returned to the Native Query Block. (Case # 1761083)
SCSF-24
Individual record errors were causing Batch Processing jobs to fail with a fatal error instead of just recording the failed record errors and continuing. (Case # 01725689)
SCSF-21
The AcctSeed_Transaction_c entity generated errors when it was included in a Data replication app. (Case # 01729385)
SCSF-12
If the Salesforce password defined in the Connection dialog was incorrect, the Connector continued to retry when the Connection test failed until the user ended up locked out of Salesforce.
Version 1.4.1 Patch 1
Released June 25, 2019.
New And Noteworthy
There are no new features in this release.
Closed Issues
SCSF-70
Integration apps with mapped relationship fields based on External IDs were not being set when the Integration app executed even when the source fields contained data. (Case # 01776960, 01777223, 01777292, 01777698, 01779615)
Version 1.4.1
Released: June 14, 2019.
New And Noteworthy
There are no new features in this release.
Closed Issues
74625
Data replication apps generated errors when attempting to replicate entities with related entities that had long names. (Case # 69265, 01755853, 01757729)
SCSF-29
Resetting metadata generated errors for users that were upgraded to Salesforce Summer '19. (Case # 01773936, 01773091, 01772991, 01768030, 01767481, 01764564)
SCSF-33 / SCSF-51 / SCSF-22 / 73120
The Salesforce Connector interpreted a custom numeric Salesforce fields as type Double64 causing numbers inserted into that field to be rounded. (Case # 1729060, 68940)
Version 1.3.2
Released July 2, 2018.
New And Noteworthy
There are no new features in this release.
Closed Issues
64966 / 65420 / 65421 / 65746
Attempting to retrieve metadata from Salesforce using Salesforce API version 41 generated XML document errors similar to the following: (Case # 64739, 64861, 65094, 65331, 65609, 65789, 65826, 66117, 66137, 66289, 66421)
Severity: Error
Title:Scribe.Core.Processor.StartFetchActionObjectMetadataCommandHandler
Win32 ThreadId:7328
Message: Fetch actions and objects 1st retry error:
Exception Type : InvalidOperationException
Message : There is an error in XML document (147, 103680).
64848 / 65738 / 65744
When the Salesforce Bulk API was enabled, replicating entities that are never updated and have no LastModifiedOn date, such as LeadHistory or OrderHistory, generated errors similar to the following: (Case # 63881, 63366, 63978 )
Severity: Error
Title:Scribe.Core.Processor.ReplicationStatusProcessSupport
Win32 ThreadId:13372
Message: Execute process failed:
Exception Type : IOException
Message : Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Version 1.3.1
Released March 15, 2018.
New And Noteworthy
Added retry logic for Bulk API operations to retry the operation if an error is encountered. (60749)
Closed Issues
57955
flows where selected related entities were limited by the Return records only with this relationship setting, had a custom field configured as an ExternalID field, and were not used in field mappings for operation Blocks, generated Malformed Query errors. (Case # 62497)
60749
Increased polling times for Bulk API operations to address errors similar to the following: (Case # 62774, 63789)
An unexpected error occurred during the bulk operation Upsert. The following error has occurred in the Salesforce Connector: Data at the root level is invalid. Line 1, position 1.
61398
Enhanced error handling to address transient errors from the SalesforceAPI that in turn generated errors in TIBCO Cloud™ Integration - Connect similar to the following: (Case # 62774)
The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
61401
Enhanced error handling to address 400 Bad Request errors returned from the Salesforce API. (Case # 62774)
Version 1.3.0
Released November 29, 2017
New And Noteworthy
- Support for Salesforce API versions 38 through 41. (30070, 52141, 52172)
- For Data replication apps, the Salesforce Connector now uses the SystemModStamp date field instead of the LastModifiedDate field to select only new or updated records for replication. The SystemModStamp field was deemed preferable because it is maintained by the Salesforce system and cannot be updated or overwritten by any other process. (52507)
Closed Issues
31005 / 31430
When using a CSV text file as a source to create records in Salesforce, if Batch Processing was enabled on the Create Block, an error similar to the error shown below was generated: (Case # 87625)
Error: The length of the result output, 49, did not match the number of inputs, 50, for the Connector Create operation in process Apps Training 2015-2016.
38095 / 39014
The Connector did not allow writing a NULL value in a date/time field in Salesforce. (Case # 56492)
50651 / 50771
Data replication was attempting to query the Scribe_CaseAssignmentId virtual field which generated a fatal error and prevented the Cases entity from synchronizing.
Fall 2016 Release
Released: November 8, 2016.
New And Noteworthy
This release includes the following enhancements:
- Reduces the number of API calls the Salesforce Connector makes when modifying a flow or refreshing metadata.
- Includes a Native Query Block, which supports SalesforceObject Query Language (SOQL) for constructing query strings.
- Enables automatic execution of Salesforce Case Assignment rules when a Case is created. Batch processing may have some performance implications, and some rules may not be available in bulk mode.
- Supports Salesforce API version 37.
With this upgrade of theTIBCO Cloud™ Integration - Connect Connector for Salesforce to support the Salesforce API v37 there may be some backwards incompatibilities with the upgraded Connector and the prior version of the Salesforce API (v33 and below) that could cause integrations to fail. Some users have reported the following error:
A fatal error has occurred in the Salesforce Connector: There is an error in XML document (87, 4641). | Details: at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
To workaround this issue, follow these steps for each and every Salesforce Connection in all of your Organizations:
- Open the TIBCO Cloud™ Integration - Connect Salesforce Connection dialog.
- Change the Salesforce URL to use the V37 API instead of v33.0 and below by entering the following URL:
https://login.salesforce.com/services/Soap/u/37.0
- Test and save the Connection.
- From the Connections page, reset the metadata for each Salesforce Connection either by right-clicking the Connection and selecting Reset Metadata or by selecting the Connection and clicking the Reset Metadata button at the top of the Connection page.
- Wait a few minutes for metadata to be reset and run the flow or app again.
Closed Issues
75587 / 8821
A large number of API calls occurred when modifying a map or refreshing metadata.
Because Salesforce enforces an API call limit for a 24-hour period, excessive API calls could cause integrations to stop and impact client business. We significantly reduced the number of API calls made when you modify a flow or refresh metadata.
78394 / 10937
Salesforce Upsert error when the number of records processed was greater than the batch size.
When a fatal error occurred in a batch operation, the text reporting the error did not indicate the specific row that caused the error. Now, fatal errors report more specific information about the failing rows.
Fall 2015 Release
New And Noteworthy
The Salesforce Connector was installed automatically with any agent installation. In this release, the Salesforce Connector has been moved to the TIBCO Cloud™ Integration - Connect Marketplace. (1802, 1809)
Closed Issues
5399
The Salesforce connector could not convert values in culture based fields, such as currency fields, to culture neutral values, when the culture format was not en-US. (Case # 73924 )
5400
Testing the connection with an on-premise agent failed to parse the URL and generated errors in TIBCO Cloud™ Integration - Connect. (Case # 73334 )
April 3, 2015 Release
New And Noteworthy
- Support for Salesforce API Version 33.
- Support for Insert, Update, and Upsert operations with relationships.
- Added an option on the Salesforce Connection dialog to automatically refresh metadata on every run for Data replication apps. If enabled, this option uses more Salesforce API calls because the metadata must be retrieved from Salesforce. However, if you frequently modify your schema, enabling this option ensures that your maps have the latest metadata.
Closed Issues
There are no closed issues in this release.
June 14, 2014 Release
New And Noteworthy
- Updated the connector to support Salesforce API Version 30.
- Added support for new Order and Order Item entities.
Closed Issues
8566
Running large queries on Salesforce using Connect cloud agents sometimes caused time out errors. (Case # 58388)
8684
Queries against Salesforce entities with very large number of records were occasionally timing out. (Case # 59351)
July, 2014 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
8792
If you were using an Advanced map that used relationships to query for child records, only the first 1999 child records were returned. (Case # 59343)
March 2014 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
8395
Bulk API for Salesforce was not working properly with Advanced flows (Case # 56963)
August 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
7532
An error occurred while processing insert operation. Details: Character reference "" is an invalid XML character (Case # 51909)
June 22, 2013 Release
New And Noteworthy
- Support to include deleted items (from the Recycle Bin) in query results.
- Support for Salesforce API Version 28.
Closed Issues
7421
Salesforce non-queryable entities (e.g., ActivityHistory) show edup in replication results with no records (Case # 51404).
7441
Using ISNULLOREMPTY and ISNULLORWHITESPACE on string fields only. If you used these functions with a non-string field, if the incoming value was NULL, the function returned FALSE .
7475
Show Statistics was not showing all maps (Case # 51574).
7494
Stop solution function was no longer working, stop command was being ignored (Case# 45943, 51125, 51721).
April 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
7361
Batch upsert in integration solutions generated a runtime error of “Duplicate external id specified” (Case # 51116)
March 2013 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6762
Deleted records were not being soft deleted in replication database (Case # 49053)
6874
Data replication runs for both Salesforce and CRM were showing 1 more record processed than should be for the job.
July 2012 Release
New And Noteworthy
There are no new features in this release.
Closed Issues
6308
After an agent upgrade, if Use Salesforce Bulk API for initial replication was selected on the Salesforce Connection dialog, the checkbox was cleared. However, the associated apps continued to use the Bulk API . In addition, when using this Connection in a new map for an Integration app, when you tried to load Salesforce entities you received an error similar to the following:
"Unable to retrieve metadata. There is an error in XML document (1, 7113)”.