Deploy Direct-DMO Customizations to Production with Sandbox Mergeback (Beta)
Starting in Winter '26, you can package and deploy customizations containing direct data
model object (DMO) relationship metadata from sandbox to production environments.
Required Editions
Note This feature is a pilot or beta service that is subject to the Beta Services Terms at
Agreements - Salesforce.com or a written Unified Pilot Agreement if executed by Customer, and
applicable terms in the Product Terms Directory. Use of this pilot or beta service is at the
Customer's sole discretion.
This process is specifically for deploying direct-DMO custom lookup fields from sandbox
to production orgs.
Important If your Lightning Page contains a dynamic related
list, do not change the activation status of the page. Activating a page during this process
prevents you from installing this new change set.
In your sandbox org, open Setup and navigate to Outbound Change Sets.
Create a new change set.
Add foundational CRM metadata, such as custom objects and custom fields, as well as Data
360 metadata in the form of a data kit. In this change set, you must manually configure the
metadata type FieldSrcTrgtRelationship for your
desired direct-DMO relationship.
In the Change Set Components section, click View | Add Dependencies. Then, add your direct-DMO custom lookup field to the changeset.
Navigate to the target org and open the Inbound Change Sets list.
In the Change Sets Awaiting Deployment section, deploy your change set. If the deployment is successful, you can mergeback CRM customizations that reference the relationships you added.
Create a new outbound change set and add your customizations.
.
Upload the changeset to the target org.
Install the changeset in the target org.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.