We have installed DocuSign eSignature for salesforce managed package in our org. There is a requirement to access related list details and display them within a table dynamically on a DocuSign Envelope Template. Opportunity (Source Object) > Clean Energy Application custom object (Reference) > Clean Energy Application Line Item custom object details for each line item (Child).
Challenges:
DocuSign Merge Field Limitation: Currently, it is not possible to create a merge field within DocuSign that can pull and display the CEA line item details from the Clean Energy Application. This limitation exists both within the DocuSign app and within the Document Custom Fields in the DocuSign web account.
Static Document Template: In the current template design, the document uploaded is static, which prevents the dynamic display of CEA line item details for each application.
Given these challenges, is there any way to achieve the desired outcome? I would greatly appreciate your support and any suggestions you can provide.
Did you customize the data path manually? Or did you use the data path that is provided to you after you select the lookup field, related fields etc. on the “Place Fields” step? I recommend drilling down in the Place Fields step then copy the field path and put that into your Tablerow field. And without seeing your Word document as well as seeing the data structure in y our Salesforce org, it’s a bit difficult to assess and provide feedback that’ll fix your issue.
Yes absolutely. Please check out these two links. The first is to another community post with feedback in the comments, and the other link is to our Docusign Gen for Salesforce admin guide:
In the eSignature Envelope Template Configuration, navigate to the Recipients tab, and make sure that the “Role Name” of your recipient is “Signer 1” or “Signer 2” or “Signer 3” etc. These are default role names that our system recognizes and knows to look for anchored/autoplaced fields to place for them. For example, a \s1\ on your document would place a signature field on the document that’s assigned to your “Signer 1” recipient. Or a \s2\ would place a signature field for “Signer 2”, and so on.
Given the types of questions you’re asking, I recommend speaking with your Docusign sales team about our various consulting and implementation service offerings that can help provide you with personalized guidance.
The Docusign eSignature for Salesforce integration can’t produce dynamic tables. Meaning, it’s unable to dynamically generate 1 row if there’s only 1 related list record, or 5 rows if there are 5 related list records, etc. It assumes the underling document is static, meaning there’s a fixed number of rows. Within that context, you can certainly denote which related list row you want to merge in information from. Some customers who have a need to show up to 5 rows of data will build out the rows and merge fields, and set rows 2-5 to “read only” so that they disappear off of the document if there’s no corresponding related list record to pull in information from. So there is a workaround, but how to approach it and whether or not it’ll work for you depends on the use case and other technical or business requirements.
That said, Docusign also has another Salesforce product called “Docusign Gen for Salesforce” which allows for dynamic document generation, and it can certainly produce dynamic tables with a varying number of rows. This is a separate product that requires its own licensing. Many customers who have both Gen and eSignature will use Gen to produce dynamic documents (like ones with a varying number of table rows), then link that with their eSignature Envelope Template Configuration to pull in that most recently generated document into the “envelope” to then route for signature and/or other data collection.
Hi @Jesse.Morgan, Thanks for the detailed explanation provided.
Yes, I have started exploring DocuSign Gen to create a gen template using Microsoft word document. However, I’ve encountered a few challenges and would greatly appreciate your guidance:
1> I attempted to create a custom table and DocuSign signature field with XML tags as shown below, but unfortunately, it’s not working as expected: <# <TableRow Select="/Opportunity//Clean_Energy_Applications__r//Clean_Energy_Application_Line_Item__r" /> #><# <Content Select="./CE_Quantity__c"/> #>
Just to clarify, Opportunity is the root object and has a lookup to the Clean Energy Application custom object.
The Clean Energy Application object has a related list of Clean Energy Application Line Item records, which I am trying to display in a table.
2>Is it possible to calculate and display the totals of column values for all the related CEA Line Item records in the last row of the table? 3> I tried linking the DocuSign Gen template with the DocuSign Envelope template.
When designing the Gen template, if I place a DocuSign Signature field, how can I assign that signature field to a specific recipient defined in the signing order of the envelope template?
My concern is that the DocuSign Gen template comes first, followed by the envelope template, so I’m unsure how to specify fields for a particular recipient when designing the templates.
I truly appreciate your help with this. Thank you in advance for your time and support!
Did you customize the data path manually? Or did you use the data path that is provided to you after you select the lookup field, related fields etc. on the “Place Fields” step? I recommend drilling down in the Place Fields step then copy the field path and put that into your Tablerow field. And without seeing your Word document as well as seeing the data structure in y our Salesforce org, it’s a bit difficult to assess and provide feedback that’ll fix your issue.
Yes absolutely. Please check out these two links. The first is to another community post with feedback in the comments, and the other link is to our Docusign Gen for Salesforce admin guide:
In the eSignature Envelope Template Configuration, navigate to the Recipients tab, and make sure that the “Role Name” of your recipient is “Signer 1” or “Signer 2” or “Signer 3” etc. These are default role names that our system recognizes and knows to look for anchored/autoplaced fields to place for them. For example, a \s1\ on your document would place a signature field on the document that’s assigned to your “Signer 1” recipient. Or a \s2\ would place a signature field for “Signer 2”, and so on.
Given the types of questions you’re asking, I recommend speaking with your Docusign sales team about our various consulting and implementation service offerings that can help provide you with personalized guidance.
Thank you so much for your response. I am able to progress on some of the issues with the tips given.
1> I tried by copying the field path and put that into Table row field. It worked for me now.
2> For currency fields, sum function is not working for me. But when I tried for Number fields as mentioned in other community posts, it worked. Please guide me in case you have any idea on currency fields. Attached screenshot.
3> Once I changed the Role Names as you have shared, it worked for me.
4> Concat function is not working as expected when I tried doing it as per the article below. Please let me know if I am missing something. Attached screenshot.
It looks like you’re trying to define the full data path when it’s already being defined by your TableRow tag. Simplify the data path, similar to how you fixed #1.
I hope that helps! If it does, please consider marking one of my responses as “best”.
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.
Join the Docusign Community by logging in with your Docusign developer or customer account credentials.
Don’t have an account? You can create a free one when registering.
Note: Partner-specific logins are not available yet. Partners should log in as either a customer or developer
Docusign Community
You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.