Loading
Salesforce Document Generation
Innehållsförteckningar
Filter (0)Lägg till
Välj filter

          Inga resultat
          Inga resultat
          Här är några söktips

          Kontrollera stavningen av dina nyckelord.
          Använd mer allmänna söktermer.
          Välj färre filter för att utöka din sökning.

            Sök hela Salesforce-hjälpen
            Sök hela Salesforce-hjälpen
            Context Mapping for Document Generation

            You are here:

            1. Salesforce Help
            2. Docs
            3. Salesforce Document Generation

            Context Mapping for Document Generation

            Map the structure defined in a context definition to actual data sources so document templates can retrieve values at runtime. A context mapping links each node and attribute to specific Salesforce fields and objects. When editing a context mapping, use Edit SObject Mapping to access and update the appropriate mapping. Make sure to update the input mapping as well to keep it in sync. Make sure the input mapping names match the attribute names. If they don’t match, data for those attributes won’t be hydrated.

            Required Editions

            Available in: Lightning Experience
            Available in: Professional, Enterprise, Unlimited, and Developer Editions

            For example, to generate a contract document that includes product line items, create a context mapping that links the Contract node to fields such as Contract.StartDate, Contract.Status, and Contract.ContractNumber. Add a separate SalesContractLine node and map it to attributes like ProductName, Quantity, UnitPrice, and TotalAmount. These mapped fields allow the document template to populate tokens such as {{StartDate}}, {{Status}}, and {{ProductName}} with values from the associated Contract and SalesContractLine records. If your template includes editable fields like contract Status, you can use a data true-up token such as {{DT_Status}} to support updates to data-true fields after document generation.

            As Contract has a one-to-one relationship with Account, you don’t need a separate node for Account. Instead, you can reference Account fields directly from the Contract node using nested field paths. For example, map Contract.Account.Name to {{AccountName}} and Contract.Account.BillingCity to {{BillingCity}}. Context Service supports up to 5 levels of nesting, to have access to deeply related fields within the same node if needed.

            Additional Notes for Context Mapping

            • Create the context definition, define its structure, and complete the mapping before activating it.
            • Map all nodes first, followed by their corresponding attributes.
            • Ensure at least one node and one attribute are mapped to save the context mapping.
            • In context mapping with hierarchical child nodes, the Omniscript uses the parent object ID and not the child object ID. For example, in a Contract Contract Line Items mapping, the Contract ID is used. The same behavior applies when using the DocGenAdditionalInput field in a Document Generation Process (DGP); the parent object ID is used, not the child field’s ID.

            Modify a Context Mapping

            • To add or update nodes in a context definition, deactivate it first. After making changes, go to the context mapping screen and click Update SObject Mapping to refresh the mappings.
            • Create a Context Mapping for Document Generation
              Configure a context mapping to link nodes and attributes from your context definition to Salesforce fields and objects. These mappings allow document templates to populate tokens with runtime values from related records.
             
            Laddar
            Salesforce Help | Article