Deep Clone uses Context Service to retrieve and map data between Sales Agreements and
its child entities during the cloning process. It includes an Out-Of-The-Box (OOTB) context
definition and mapping.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer
Editions
To support custom fields and additional related entities, Salesforce admins must extend the
context definition and configure the necessary mappings.
Extend Context Definition: In Context Service, extend the existing Out-Of-The-Box (OOTB)
context definition by adding new nodes or fields to support custom fields or related
entities. Then, map the newly added fields and nodes between the source and target Sales
Agreements to ensure the deep clone accurately copies the required data. See Extend Context
Definition.
Add Custom Fields: Use Object Manager in Salesforce to add any custom fields to the Sales Agreement
object or its related child objects (e.g., Product, Schedule, Attribute),
depending on your requirements. Before adding custom objects ensure to extend context
definition and create mapping for those nodes.
Extend Context Definition Extend the Out-Of-The-Box (OOTB) context to create a custom context definition with additional attributes, without modifying existing ones. Similarly, you can extend the mapping to include additional mappings, without changing the existing ones.
Create Procedure Plan Use the procedure plan definition to determine the correct context definition and mapping required for the deep clone.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
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.