Loading
Salesforce Document Generation
Table des matières
Filtres (0)Ajouter
Sélectionner des filtres

          Aucun résultat
          Aucun résultat
          Voici quelques conseils de recherche

          Vérifiez l'orthographe de vos mots-clés.
          Utilisez des termes de recherche plus généraux.
          Sélectionnez moins de filtres pour élargir votre recherche.

            Recherchez dans toute l’aide de Salesforce
            Recherchez dans toute l’aide de Salesforce
            Considerations for Data Transformation with Data Processing Engine for Document Generation

            You are here:

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

            Considerations for Data Transformation with Data Processing Engine for Document Generation

            Understand the requirements and guidelines for configuring transformations by using Data Processing Engine (DPE). Learn how configuration impacts hierarchy, grouping, and calculated data in a generated document.

            Required Editions

            Available in: Lightning Experience
            Available in: Professional, Enterprise, Unlimited, and Developer Editions
            • Include all fields that define relationships. Use these fields to build a hierarchy and link records.
              • Object ID, for example Quote ID
              • Parent reference
              • Self-lookup fields for bundles and groups
            • Subtype and writeback structure
              • One subtype node per context node
              • One writeback per subtype
              • Use Composite Writeback to merge outputs
            • Select JSON structure:
              • Simple: Flat data, for example, Quote
              • Hierarchy: Parent-child relationships
              • Group: Categorized data
            • Use join to merge computed values with existing data. Use join to:
              • Add default values
              • Add formula fields
            • Include identifier fields to merge correctly data during join. For example:
              • Quote ID
              • Quote Line Item ID
            • Make sure that the template matches the JSON structure:
              • Use related records for child data
              • Use children for nested hierarchy
              • Use grouping fields as headers
            • Select only required fields in subtype nodes because only selected fields are included in the output JSON.
            • Transformation access:
              • Only Salesforce admins with DocGen Designer licenses can configure transformations.
              • At run time, users can execute transformations but can’t configure them.
            • Support multiple nested levels, including:
              • Parent-child groups
              • Nested bundles
            • Grouping behavior
              • Works on parent-level and child-level data, such as Quote and Quote Line Items.
              • Make sure that the grouping field is mapped in the Context Definition.
            • Alias guidelines
              • Use clear and meaningful alias names, for example, Price.
              • Use the same alias consistently across formula node, join node, writeback, and template.
              • Alias names are case-sensitive and must match template tokens exactly.
              • Incorrect alias-mapping results in missing values in the generated document.
             
            Chargement
            Salesforce Help | Article