Snap Pack history: Salesforce
|
|
|
Updates |
|---|---|---|---|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with Salesforce JWT OAuth accounts where authentication failed with invalid_grant – login rate exceeded errors during pipeline execution. Implemented a token caching mechanism to reuse the token until expiration, preventing errors that occurred due to token generation on every execution. |
|
|
|
Enhanced the Salesforce OAuth2 Account to support the Password and Client Credentials grant types for all Salesforce Snaps.Enhanced the Salesforce Snaps (Create, Lookup, Poller, Subscriber, SOQL, Update, and Upsert), with the following retry settings that enable you to control how the Snaps handle connection and error responses.Number of RetriesRetry Interval (seconds) |
|
|
|
Fixed the Salesforce Subscriber Snap stall issue caused by an expected disconnect from the Salesforce server when multiple pipelines simultaneously consumed messages from the same Salesforce channel, particularly after encountering 403: Unknown client errors. |
|
|
|
Added internal retry policy to the OAuth2 token refresh mechanism to address intermittent 401 unauthorized access errors in the HTTP calls made by the Salesforce SOQL and Salesforce Read when fetching metadata from the SFDC. This ensures retries work correctly when token issues occur. |
|
|
|
Fixed a memory leak issue in Salesforce Wave Analytics caused by the RestHttpClient object. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Enhanced the Salesforce JWT OAuth2 Account to allow connections to Salesforce endpoints through a proxy configuration. This prevents socket connection timeouts that occur because of direct connection attempts.Fixed an issue with the Salesforce Read and Salesforce SOQL where thread locks were caused by cache load operations and the lack of connection and socket timeouts in Salesforce Snap HTTP requests. |
|
|
|
Added internal retry policy to OAuth2 token refresh mechanism to address intermittent 401- unauthorized access errors in the HTTP calls made by the Salesforce Bulk Create when fetching metadata from the SFDC. |
|
|
|
Fixed memory leaks caused by the RestHttpClient objects in Salesforce.Fixed the Salesforce Update to prevent using an invalid URI when the Salesforce Account login fails. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Enhanced the Salesforce Subscriber to support subscribing to custom channels that collate events from multiple related sources in one place for the subscribers.This enhancement broadens the scope of building event-driven integrations to consume real-time Salesforce event data and workflows through custom configurations. This reduces latency and the need to poll for events. |
|
|
|
Fixed an issue in the Salesforce Bulk Query that displayed a 401 error during metadata calls. Now, the Snap refreshes the OAuth2 token and retries the metadata call on encountering a 401 error. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Added Salesforce JWT OAuth2 Account to the Salesforce Snap Pack, enabling a secure and efficient server-to-server authentication. |
|
|
|
Implemented a redirect strategy for all Salesforce snaps to ensure valid URL redirection when Lightning URLs are used. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed the vulnerabilities in CXF library dependencies within the Salesforce Snap Pack to enhance security and ensure reliable functionality. |
|
|
|
Fixed an issue with the Salesforce Lookup, Salesforce SOQL, and SOSL Snaps, where errors were not routed to the error pipeline when Route Error Data to Error View was enabled, and a referenced expression variable was missing in the upstream or pipeline parameters. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Salesforce Publisher where an invalid session triggered infinite retries, resulting in many open file descriptors that eventually crashed the node. |
|
|
|
Fixed an issue with the Salesforce SOQL where the URL encoding was improperly applied to sandbox instance URLs. Now, the Snap ensures URL sandbox instance URLs are properly encoded. Important: Breaking change from Salesforce
Salesforce is retiring some of the hostnames for non-enhanced domains from August 2024:
When deploying a new My Domain, including enhanced domains, Salesforce automatically redirects previous URLs. For detailed information, such as hostname formats for legacy (non-enhanced) domains, refer to the Prepare for the End of Redirections for Non-Enhanced Domains. To align with Salesforce’s redirection changes for non-enhanced domains, the classic URL format (https://snaplogic--devqa.my.salesforce.com/) is no longer supported for Sandbox environments. As a result, any existing Salesforce pipelines using classic URLs will stop functioning as before. Workaround To run your pipelines successfully, you must append Learn more about the enhanced domains deployment by Salesforce. |
|
|
|
Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward-compatible. |
|
|
|
Fixed authentication issues with the Salesforce Subscriber in the Ultra Pipeline to ensure the Snap reauthenticates and reconnects as expected. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Enhanced the Salesforce Bulk Create, Salesforce Bulk Delete, Salesforce Bulk Query, Salesforce Bulk Update, and Salesforce Bulk Upsert to include the complete error details under the original object that contains the copies of the failed input records. |
|
|
|
Fixed an issue with the Salesforce Mutual Authentication Account where the 8443 port was not used while authorizing the account. Now, the access token request uses the 8443 port for authorizing the Mutual Authentication Account. CAUTION: Breaking change
Prior to 436patches25192, the Salesforce Mutual Authentication Account supported default Login URLs such as https://login.salesforce.com and https://test.salesforce.com. From 436patches25192, this account no longer supports the default Login URLs—your existing pipelines using the Mutual Authentication Account with the default Login URLs might break. To prevent this breaking change, you must provide a valid Salesforce Login URL as part of your account configuration. |
|
|
|
Enhanced the Salesforce Bulk Query with expression support for the Include Deleted Records checkbox. |
|
|
|
Fixed an issue that caused the input stream to not close properly, which resulted in stale connections. |
|
|
|
Enhanced the performance of the Salesforce Bulk Query with a new Maximum threads field. This field enables you to download query results simultaneously in multiple threads. |
|
|
|
Enhanced the Salesforce Read by adding expression enablement to the following checkboxes:
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue where a long-running pipeline containing the Salesforce Subscriber would suddenly stop responding. |
|
|
|
Improved the Salesforce Bulk Upsert error messages by limiting the length of the reason displayed with the error. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Salesforce SOQL and Salesforce Read where the Match Data Type checkbox selection was not honored if the Salesforce API field was set to Bulk API. |
|
|
|
The Display null or empty values as null checkbox in the following Salesforce Snaps enable you to control the display of empty string and null data as null in the output preview. The Salesforce Account no longer validates an invalid URL but fails with an error:Error processing table usr__c = ErrorDto{failure='Failed to perform AutoSync for table usr__c |
|
|
|
Fixed an issue with the Salesforce Read that was causing an error for the Time data type. |
|
|
|
The Salesforce Create, Salesforce Update, and Salesforce Upsert now include an Apply active assignment rules checkbox so you can control whether to use assignment rules for the selected object |
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
|
|
|
|
The Salesforce Bulk Create, Salesforce Bulk Delete, and Salesforce Bulk Update are now working as expected without displaying the error Error while processing Data and without returning 301-error while processing the data. |
|
|
|
The Salesforce Read now correctly parses the 2-byte UTF-8 characters in Windows OS in the PK chunking mode. |
|
|
|
|
|
|
|
|
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with Salesforce Snaps where the Service Version could not be retrieved from SFDC due to a blocked URL, failing the Snap execution. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Salesforce Subscriber where the Snap was unable to re-subscribe to a topic if it did not receive any message for 72 hours —stopped and displayed an error message. With this fix, the Snap automatically sets the Replay ID value to -2 when:
|
|
|
|
Fixed an issue with Salesforce accounts, where an account password containing special characters and an empty security token was not properly encoded and the account was not validated. |
|
|
|
Fixed the following issues with Salesforce Snaps:
|
|
|
|
|
|
|
|
Enhanced the Salesforce Subscriber with improved resilience to network failures and fixed an issue with duplicate documents. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |
|
|
|
Fixed an issue with the Salesforce Read where the retry fields do not work as expected when a Pipeline has more than ten Snaps. |
|
|
|
Enhanced the Salesforce Read to allow you to add an optional second output view that exposes the schema of the target object as the output document. The output view of the Snap has a minimum of one output and a maximum of two outputs. |
|
|
|
|
|
|
|
|
|
|
|
Fixes an issue in Salesforce Bulk Upsert, Salesforce Bulk Update, and Salesforce Bulk Create that fail to process Related object and Related external ID values by modifying the input schema that formats the CSV data.
Warning: Potential Breaking Change
This Salesforce Snap patch contains an issue affecting the Salesforce Subscriber and Salesforce Publisher. If you do not use these Snaps in your Pipelines, then you can use this patch version. Else, we recommend you to not use this patch version as Pipelines will fail. We will fix this issue soon in an upcoming patch. |
|
|
|
Updated and certified against the current SnapLogic Platform release. |