Loading

Omnistudio Releases

Publiceringsdatum: Apr 22, 2026
Beskrivning

As of Spring '25, the Omnistudio managed package link is provided only for the latest version. Patch releases are cumulative, and you can use a patch for a new installation.

 

For installation links to versions older than the current release, contact Salesforce Customer Support.

NOTE: If the production and sandbox package links don't work, right-click the link, and open it in a new tab or window.

Before you install a managed package:

Current Release

IMPORTANT: Salesforce delivers new features three times per year (during the seasonal releases: Spring, Summer, and Winter) via automatic upgrades. After you install the current release, subsequent releases are delivered automatically. 

Automatic upgrades are required starting in Spring '24. For more information, see Salesforce Industries Automatic Upgrade

Salesforce core releases apply automatically to orgs with the Omnistudio standard runtime and don't use managed packages. 

Major ReleaseVersionRelease DateRelease Notes
Spring '26

260.10.1

April 22, 2026

Previously, when an object contained fields with a namespace and without a namespace, the system included both fields in the generated query. As a result, Data Mapper execution failed if the user had access to only one of the fields, especially after recent security enhancements. In some cases, this caused a “no access” error even when the conflicting field was not explicitly referenced by the user. This issue has been fixed. The query builder now detects namespace conflicts between fields. When such a conflict is identified, the query is executed in system mode, and any inaccessible fields are removed before processing.

 

Production Package
Sandbox Package

Spring '26

260.13

Salesforce Core Release

April 22, 2026

Previously, Apex class namespace usage was enforced as mandatory, which also altered the JSON response structure by introducing an additional result node and required customers to update their integrations. This issue has been fixed. Namespace usage is now optional, and the JSON response returns to its original structure when the namespace is not used.

Spring '26

260.10

 

April 1, 2026

In client-side DOCX Omniscript document generation, users experienced an issue where the preview screen showed a continuous loading state, PDF conversion didn’t initiate, and document generation stopped without any visible errors. This behavior was caused by recent Chrome browser updates that changed how file data is validated. This issue is fixed by correcting that required file type processing for document generation works as expected across supported browsers.

 

Production Package
Sandbox Package

Spring '26

260.6.2

Salesforce Core Release

 

February 25, 2026

Previously, when a user accessed an Omniscript via a Save for Later URL, the system incorrectly re-invoked Integration Procedures that were already invoked in previous steps. This occurred even when the Save automatically when users click Next setting was enabled. This issue has been fixed.


Previously, the export and import functionality failed to work causing issues with Omnistudio deployment. This issue has been fixed.

Spring '26260

Omnistudio Spring '26 Release Notes

 

 

Knowledge-artikelnummer

000394906

 
Laddar
Salesforce Help | Article