Skip to main content
Feedback

Salesforce REST changelog

Updated 

Changelog

2026-11 (Version 13, Runtime release)

  • Added a Query Parameters field to the Upsert operation for REST API and Composite REST API modes (not Bulk API V2.0). Set updateOnly=true to return an error instead of creating a record when no match exists. This requires an External ID Value and a Service URL on Salesforce API v61.0 or later. A blank External ID Value with updateOnly=true returns an application error. You can override parameters per document with the Query Parameters dynamic operation property. In Composite REST API mode, only the first document in each batch is used. (CONC-16611)

This feature is not in the runtime release.

  • Updated the Parent Entities Depth and Child Entities labels, options, and help text in the Query operation, so you can see how each setting affects parent and child data in your profile.

This enhancement is not in the runtime release.

  • Resolved an issue where the connector was not honoring the “Batch Count” configuration for greater than 100 documents in the Create, Update, Upsert, and Delete operations.

  • Resolved an issue where the Query operation omitted direct parent objects from the Fields tab when Parent Entities Depth was 1 and child entities included parents. The Fields, filter, and sort panels now show all profile relationships.

These fixes are in the runtime release.

2026-09 (Version 11, Current)

New Feature

  • Added a Scope field to the OAuth 2.0 section of the Salesforce REST connection, so you can set OAuth scopes for the Authorization Code and Client Credentials grant types. (CONC-18277)

  • Added support for retrieving actual blob content on document fields such as VersionData. (CONC-16857) (CONC-15898)

These features are not in the runtime release.

Fixes

  • Resolved an issue where the connector returned a null value for the Application Status Code Document Property when the HTTP response status was not in the 200 range. (CONC-11620) (CONC-17305)

  • Resolved an issue where the UPSERT operation would fail when the field data contained a ? character with Composite REST API enabled. (CONC-11635) (CONC-17305)

  • Resolved an issue where the Return Application Error Response was not passing error messages to the next shape during the QUERY operation and was throwing a hard exception and halting the process. (CONC-16680)

These fixes are not in the runtime release.

2025-05 (Version 11)

  • You can now provide a Sandbox URL in your connection when you choose User Credentials as your authentication type.

  • Boomi updated the Jackson library to version 2.15.4 to prevent errors when building payloads for large query statements.

2025-05 (Version 10, Current)

  • You can now provide a Sandbox URL in your connection when you choose User Credentials as your authentication type.

  • Boomi updated the Jackson library to version 2.15.4 to prevent errors when building payloads for large query statements.

2025-03 (Version 9, Reverted)

Boomi removed new features from the March Platform release after the Runtime release. If you applied version 9 during the Runtime release, be aware that Boomi will revert you back to version 8.

2024-08 (Version 8)

  • Necessary runtime packages are now packaged with the connector.

2024-06 (Version 6)

  • The Salesforce REST connector is now in General Availability (GA).

  • A new overridable operation field, External ID Value, indicates the object to update in the Upsert operation when the Operation API is configured as REST API. If you leave this field blank, the connector creates a new object. The connector ignores this field when you set batch count greater than 1.

  • A new grant type when you authenticate using OAuth 2.0, Client Credentials.

  • A new option in the Operation API dropdown box for the Create, Delete, Update, and Upsert operations, Composite API.

  • The operations names for the connector were updated to use Title Case. Although these changes will not affect process executions, if you want to update your process in the build canvas, you will need to re-select the action and operation component in the connector step before deploying.

2024-04 (Version 4)

  • The Create, Delete, Update, and Upsert operations will throw an Application error when operations using the Composite API fail.

  • The @Type attribute is now automatically injected into the records node when executing a Composite API request (API REST, batch size > 1) for the Create, Update, and Upsert operations.

On this Page