Skip to main content

#DocuSign For Salesforce0 utenti parlano di questo argomento

Is anyone else running into issues when trying to get the DocuSign eSignature for Salesforce? Even after creating a new account and Trailblazer profile and a Developer edition too, I still get this error message when trying to download it. Any help will be appreciated. Thanks   

Docusign eSignature for Salesforce

 

 

 

#DocuSign For Salesforce

3 risposte
0/9000

Hi all,

 

I'm an absolute novice with Docusign and trying to create my first Docusign Gen Template from the opportunity object. Those merge fields are displaying fine but the merge fields from the related list for the custom object 'Hire' are showing this error: 

 

TemplateErrorExists:XPathException: XPath expression (./Activity_Name__c) returned no results

 

The hire record is the child in the master-detail relationship with the opportunity record. 

 

Furthermore, the hire name field that I'm trying to use as the document reference returns the error:

 

TemplateErrorExists:TableRow tag must be placed in a table.

 

A colleague who is much more experienced with Docusign than myself has had this issue with related list fields previously and has given up without resolving it but I have many documents to create that use these custom object fields so would really like to get to the bottom of it!

 

All ideas and guidance welcome, thank you!

 

#Docusign Gen #DocuSign For Salesforce

5 risposte
  1. 11 apr 2025, 11:00

    @Kim Sidaway

    hey Kim, having stuggled with a similar issue I finally found a resolution. 

     

    The solution is to use the whole expression not just the partial bits that are provided in the Docusign UI - well at least for a Content Select type. In my case, the key was ensuring that there are // (double slashes) between each of the different Object Levels across a relationship. When I tried with just a single I got the no results error you were also receiving. 

     

    In my instance, I needed to return a single Contact's name on a document initiated on the Account via the AccountContactRelations object. This was the entire expression I used in my template:

    <# <Content Select="/Account//AccountContactRelations//Contact.Name" /> #>
0/9000

I have to show only the parent QLI in the Document adjusted via DocuSign, but I'm getting the Child QLI Also. 

 

#DocuSign For Salesforce  #Docusign Gen  #Docusign

0/9000

Hello, DocuSign eSignature for Salesforce admins, 

I am working on building a DocuSign envelope template inside Salesforce using DocuSign App Launcher(DAL), in this template, I have a requirement to pre-populate data into the document from three sources, the source object itself, its parent record, and its child record. I could add merging fields for the source record, and its parent record, but my question here is for children, if the source record has multiple children, how does DocuSign know which child record to retrieve the data from it? Is it the most recent child record or the first created one or what? On their documentation page, nothing mentioned about this point 

https://support.docusign.com/s/document-item?language=en_US&bundleId=srl1586134368658&topicId=zce1616797759905.html&_LANG=enus

 

 

#DocuSign For Salesforce  #Docusign

2 risposte
  1. 23 gen 2025, 21:31

    @Logan Boardman

    Thanks Logan for your response. I have created a ticket with DocuSign Support and confirmed the following :  

    DocuSign retrieves data from child records based on the Salesforce row number specified in the field's property panel. 

    When adding merge fields for child objects, you need to add the merge fields to the document multiple times, each time specifying a different Salesforce row number. This allows DocuSign to retrieve the data from the corresponding child record based on the selected row number. 

    For example, if you want to display two lines of the child object, add the merge fields to the document twice, with the corresponding Salesforce row numbers 1 and 2. 

     

    Based on the above Docusign response, the retrieved child record is based on the value of that setting,  the Salesforce row number,  under the merging field.

0/9000
  • I want to write Apex to do exactly what the docusign "custom button" does. Is this possible and does anyone have experience with this or know someone who does?

CURRENT PROCESS

  • When you create an Envelope Template in the DSFS app, it auto-generates a "custom button" that you can add to the target object's page layout. This allows a user to click this button when viewing a record detail page, which will then trigger the envelope to be created and document(s) sent for signatures based on however you configured the Template. All the button does is execute the Template settings you configured.
    • This is standard, OOTB functionality.

DESIRED FUTURE STATE PROCESS

  • I want to replicate the exact same OOTB functionality as the docusign "custom button", EXCEPT that I want it to be triggered AUTOMATICALLY when a record update action occurs. Meaning, instead of a user having to click the button to start the docusign process, I want the button to be "clicked" automatically whenever certain record update criteria are met.

MY "working draft" SOLUTION

  • After-save record-triggered flow with an Apex Action element.
    • SOURCE 1 - How to send an envelope from a Salesforce flow
    • SOURCE 2  - Sending with merge fields using the Apex Toolkit
    • The record ID, merge field values, and other required information would pass through to the envelope from the record-triggered flow, and then everything else should happen just like it is configured in the Template.

WHY

  • Because we have an application process where dozens of "agreement" pdf contracts are sent out for e-signatures every week when the are placed in status "application accepted". Right now, someone on our team has to check each day for any Applications in the "application accepted" status, then open each one, and click the "send for signatures" button on the record detail page. 
  1. The Template is set to "send now" so there's absolutely no reason for a human user to need to be involved.
  2. If the human user is OOO or just overly busy, the sending of the agreement contracts can be delayed.
  3. The volume of agreement contracts having to be sent out every week is large enough that this takes a decent amount of the human user's time. 

#Apex #Docusign #DocuSign For Salesforce #Flow

4 risposte
  1. 22 set 2024, 14:25

    @Andrew Ermon, were you able to generate Apex code for your requirement?

0/9000
3 risposte
  1. Ajaypreet Singh Saini (Grantbook) Forum Ambassador
    13 set 2024, 18:12

    Awesome!! Glad its fixed. Feel free to close the thread by selecting the accepted answer.

    Happy trailblazing

0/9000

Hi - when using a merge field in the docusign template, rich text fields pull in all the html characters. has anyone found a way to resolve this?

 

@* Salesforce Administrators * #DocuSign For Salesforce @DocuSign for Salesforce #Data Management 

6 risposte
  1. 25 lug 2024, 20:27

    Has anybody found a solution? I tried to re-create the solution from the youtube video but was running into errors. 

0/9000

Can docusign elements be stored in Salesforce fields?  I need to collect the information the customer adds to the docusign file and store it in their Salesforce Profile. Is this possible?

 

#DocuSign For Salesforce  #Docusign

0/9000

Hi all,

 

Does anyone use or know how the #Docusign eSignature System Sender works? We have installed the DocuSign Apps Launcher in our Salesforce production org and enabled it in our DocuSign trial account but we haven't seen any differences. The setting page said "Enable System sender: When enabled, this allows users who are not members of the DocuSign account to send and sign envelopes. The sender in this case will be the configured DocuSign administrator."

 

We are wondering if Salesforce users without a DocuSign license can send and sign envelopes via the DocuSign System Sender. Any ideas or insights are much appreciated!!!

6 risposte
  1. 4 ott 2023, 21:34

    Hi Coca, 

     

    After installing DAL (DS App Launcher), you can add the following permission sets to your Salesforce user login: 

    1) DocuSign CLM User,

    2) DocuSign User,

    3) DocuSign Sender

     

    That will do the trick. Also, a user with out a DocuSign account (that is a DocuSign Login) can sign a document, but cannot send a document for Signature. Because, sending a document for Signature will create a DocuSign envelop. (Well, I am talking in reference to "DocuSign CLM" package and I am not sure how the other lighter version DocuSign products work).

     

    Thanks, Ravi

0/9000