Partial Component Deployment
We’re excited to share that Essentials now supports selective merge for partial component deployments. This lets customers choose exactly which parts of a component to deploy with increased flexibility and precision.
What this enables
This feature enables a wide range of use cases, including:
Increased flexibility and precision when deploying merged work items—choose exactly which metadata content to promote in a pipeline.
Granular control for large components (e.g., page layouts, permission sets). Example: deploy a single field on a page layout while leaving others for later.
New ways to resolve deployment errors caused by metadata differences between the source and the target. Example: if a permission set references a feature available in the source but not in the target, omit the problematic permission and proceed instead of failing the entire deployment.
A simpler approach to find-and-replace. Previously, replacing an XML segment required writing complex YAML rules and applying them via deployment options—error-prone and too technical for many users. Now you can make those edits visually during a selective merge.
How it works
To use Selective Merge, open the Diff view and click More ▸ Selective Merge. A visual editor with a real-time diff between source and target will appear, where you can select or edit the resulting metadata content.
Selective Merge is available for both work items and deployments.
|
|
Licenses required
This feature requires Essentials Plus licenses.
Data Cloud Metadata Support
We've added support for two additional Data Cloud metadata types. You can now deploy Data Kit Object Dependency and Data Kit Object Template, in addition to the other 20 Data Cloud metadata types supported prior to this release.
Jira Fetching Issue
Some users reported an issue where Essentials was not able to fetch Jira issues due to a recent Jira API upgrade. The issue has been resolved successfully as part of this release.