Considerations for Context Transformation in Document Generation
Keep these considerations in mind when you design templates, configure Data Processing
Engine (DPE), and generate documents. These constraints impact how you structure context
definitions, transformation logic, and document templates.
Required Editions
Available in: Lightning Experience
Available in: Professional, Enterprise, Unlimited, and
Developer Editions
Transformation and Context Support
You can’t use context transformation when the context token processing type is Large.
Define and transform all context nodes in the transformation, even if you don’t intend to
use the nodes in the output. You can create a partial transformation.
Ordering criteria defined by using context filters doesn’t apply during context
transformation. DPE doesn’t support ordering for JSON writebacks.
JSON Structure and Token Behavior
Child-level transformations don’t support the DT_ prefix. Repeated tokens for child records
use fixed node names, such as related records and children, and aren’t prefixed with DT_.
You can’t control grouping node names or child record node names in the generated JSON. The
template must use the default node names for related records and children.
You can use multiple group-by attributes in a single transformation.
Composite Writeback
To build the hierarchy, composite writeback requires a defined relationship between nodes.
You can perform composite writeback for parent-sibling nodes only when a relationship
exists. For example, you can’t combine unrelated top-level objects, such as Quote and
Account.
Configuration and Access
Only Salesforce admins with DocGen Designer licenses can configure transformations.
You can’t preview a context transformation during creation. Validate a transformation by
running document generation with sample data.
When applying a context transformation, you must configure the Business Object Type
(businessObjectType) for Data True Up tokens. If it isn’t configured, the document
generation request fails.
Heeft dit artikel uw probleem opgelost?
Laat ons weten wat we kunnen doen om te verbeteren!
Wordt geladen
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.