Integrations

Hi All,We are currently implementing Docusign for Salesforce using the Docusign App Launcher.  Right now we have got it setup in Salesforce developer sandbox, connected to a Docusign developer/demo account.  We are specifically using Document Generation / Gen and eSignature.We have setup a dedicated integration as per the Make a Standard Salesforce User Your Integration User article, which appears to work well for eSignature and we have no issues at all.     However, we have encountered a challenge with Document Generation / Gen resulting in an error:Unable to create ContentDocumentLink for ContentDocumentId: 069S900000DzdJXXXX and SfObjectId: 500S900000IkmXXXX.T

Hello Everyone,I have the following situation:I created a template for a protocol. In it I defined a textmark for DocuSign, let’s call it /Sign1/. Since this document is a template it gets copied and the copies get edited. What I want to do now is the following:I want to put several of the copies in one envelope via PowerAutomate to signed each. The flow I created works fine and sends the envelope to the recipients who then are able to sign the documents.BUT they are required to sign each document as much times as documents are in the envelope. Like when I put 3 documents are in the envelope they have to hit the sign button three times on each documents. I guesss this is corresponding to the /Sign1/-textmarks which are in the envelope.Is there any way to work around this issue?Thanks in advanceJHu 

Hello DocuSign Community,Recently I created a new custom field in DocuSign, see below:And I used this field in Workday BIRT design, see below for testing:However, when test it , this field is never working and end user cannot edit this field but only see the text “\jayorg11\ , see below Can you please help why it is not working ? Is there anything I missed ? Regards,Jay

My org uses Docusign Gen for Salesforce to generate contracts and send them for esignature. Most of these contracts originate from the “Contract” object in Salesforce, but the documents themselves can vary greatly depending on the details of the contract in question. Our current solution has been to upload many, many different formatted Word docs into the same Docusign Gen Template. This way, there’s only a single button on the record page, and the end user is able to select which specific template(s) to use. The issue is, of course, the number of templates has started to balloon and is now a bit of a concern. Below is an example of what our end users are seeing:All of these options always default as checked, so every time someone wants to generate a doc, they must uncheck each template they don’t want to use. This has en

I am trying to create a check box in a document, utilizing docusign for e-sign. I have this set up in docusign: \YesCheckbox{r}\and I have this on my document \YesCheckbox1\ when document is launched in Workday, no check box comes up. Signature/print name/date work just fine with the anchor text. What set up might I be missing? 

I am building a DocuSign envelope template inside Salesforce using DocuSign App Launcher(DAL). I have the following two questions, please: I am adding many merge fields associated with Lead object, and one of these fields is Social Insurance Number. Based on best security practices, this field is enabled with the 'Hide text with asterisks' feature. The writeback is enabled for this field. But when the envelope is signed, the associated field on the Salesforce lead record is not updated. Is this a limit with DocuSign, or is there something wrong? For a specific merge field, I don’t want the field value to be pre-populated from the associated Salesforce field when the envelope is opened, but I want it to be written back to the Salesforce record. Is this possible?

Hello,I have a problem while connecting to DocuSign from Microsoft Power Automate. This happens when I want to define the connection on a “DocuSign Demo” component.After the login screen, I get the following error message : “Failed to create OAuth connection: ClientError: Test connection failed. Details: The format of value '1.1 hosted.websense 60d' is invalid.”In some cases it has been working, and at some point we start having htis error. This happens on different accounts. If I try to had a new connection, I get the same error message.Any idea?Best regards.

Hey all, I have created a flow that is supposed to update the respective envelope status in a SharePoint list and add the signed document to the line at the end. Unfortunately, the trigger does not work because I do not seem to have the necessary permissions. Can you tell me exactly what admin permissions need to be set so that I can use the trigger?thanks in advanceBest, Jana

We have our Docusign account linked to our CRM, which allows us to send envelopes through our CRM portal. I usually receive the email notification that a Docusign envelope is available to sign. When I click to review the document, I get an error message that says:“Envelope or Account Activation Not FoundThe envelope is not accessible at this time. The envelope may have been recalled by the sender or require additional processing. “I will also get a notification through my Docusign mobile app. When I go to sign the document, I am able to view the doc but the fields are not available and I am unable to sign. Is there a setting that needs to be toggled in order for this to come through? 

“Update document generation form fields from envelope” is not pulling dynamic content. Causes the following error:Action 'Update_document_generation_form_fields_from_envelope' failed: DocGen form fields are not found. The document 15f4f21e-e786-403a-b626-0e45eb957b9e does not have any DocGen form fields.

DS eSignature legacyI need to create a DS custom field, related to Salesforce.In DS Admin, I go to the menu 'Document Custom Fields' for a Field Creation.I check ‘relate to Salesforce', choose first the object, and then look for my field.But my SF field does not appear in the list, and I do not know why ! In SF, the field has good Field accessibility (I have checked accessibility/visibility for my user profile). I can see the field in SF. Do you have any idea ?

For the past week, when using the upload feature, using our linked Google Drive option, the options screen has a bug. We cannot scroll to find documents and the upload box is not working propertly. We figured it would be fixed, but its been like this for a week. 

I need to add completed envelope documents to Sharepoint, however we use Docusign to complete many different documents. I only want to add documents to Sharepoint that are for one specific thing (supply orders). My understanding is that I would need to add a trigger to the “When an envelope status changes” action. The two options I’ve found for triggers are the Envelope Custom Fields and the Document Custom Fields, but we aren’t able to add these to our envelopes or documents at this time.Are there any other options for the trigger? For example, the subject heading for an email? I understand this is not as reliable as the two aforementioned triggers, but I need to find some sort of workaround.

Hi Team,I hope you're doing well.I've been testing the integration of DocuSign with Microsoft Dynamics 365 CRM using a free developer account. I created a document template in DocuSign and configured merge fields using the Data Label option.In Dynamics CRM, I created a process action that uses the DocuSign document template ID to create an envelope. Within the same process, I added: An AddRecipient step, which successfully pulls the customer’s name and email from the CRM record. A MergeMultipleFields step to populate the merge fields in the document based on values from the CRM entity, referencing the same Data Labels defined in the template. The envelope is sent successfully to the recipient, and the recipient information is correctly added. However, the merge fields in the document are not being populated with the data as expected.I came across

Our org uses Docusign for eSignature and Doc Gen natively in Salesforce via the Docusign Apps Launcher v6.12. I'm attempting to modify an existing Gen Template. Specifically, I want to swap out the current Word .doc being used with a newer version. I can add the new Word doc via the "Upload Documents" stage of the process, but removing the old doc is throwing an error: "File failed to delete. Try again."When I attempt to delete a second time, the page is stuck loading, and I see the following error code:This page has an error. You might just need to refresh it. Action failed: dfsle:GenImportTemplateFiles$controller$removeFile [Cannot read properties of undefined (reading 'id')] Failing descriptor: {dfsle:GenImportTemplateFiles$controller$removeFile}I've attempted this with the same result on multiple

Would like to deploy “DocuSign for Outlook” for select users (365 integrated app). Unfortunately, it looks like it only defaults to the entire organization.  Thanks for any feedback.  

Hello Everyone, I’m able to create envelope successfully to send a document for signing using power automate. I receive the email to sign the document. I’m able to open and sign the document successfully. I also get the completion of signature email. However, when I open my DocuSign account, I don’t see the envelope anywhere, why? What am i missing? Any advise would be helpful.

Hi Team,  I am trying to create an envelope. i have added a pdf document to the envelope[pdf is generated from the word document] and recipient. then i try to add the anchor tab to the same for signature. the anchor tab string is present as a placeholder text on document. however it says anchor tab missing. is there any setup of anchor tab that i may have done wrong. 

I am using Power Automate to retrieve fields from a completed document; however, all the “radio group" fields are missing “tabLabel” and “tabId” information. Please advise.

Using a Business ProPlan, trying to valid the integration with Salesforce eSignature as a docusign administrator and a Salesforce Admin.When adding merge Fields to the envelope template template I get the bellow errorThere are numerous community threads which seem to point to raising a case with docusign - something (paid or otherwise) isn’t enabled on the Docusign side.Opening a case from here: https://support.docusign.com/s/contactSupport?Channels=3&language=en_UStakes me to The contact support link in the screen shot.Ho

Background: Now we are using Azure AD ID username@old-domain-name.com as Single Sign On to login DocuSign. And in near future, we will switch to username@new-domain-name.com. (same user ID, but different domain name). The email change will be done within Microsoft 365. Requirements & Questions: To ensure the smooth transition for the domain name change, what should we do in DocuSign? Could you please help me to understand what we should do/change at DocuSign side? A few things in my minds, but please help to list what else is required but I may miss.-         The user will use the user ID with new domain name, and same user name, to login DocuSign as usual. And we need to ensure the users can still be able to view their historical envelopes that they submitted/approved. This is CRITICAL..-         From admin side, what we should do? I found the user’s email field is not editable. How to change their mail suffix from the old one to new one? Can

hello,in our organisation, we have several word template with the same confirgurationsince the 09/04/2025 one field non longer appaers we haven’t change the word template and haven’t change de fieldthis is the formula into my words document <# <Content Select="/SBQQ__Quote__c/Tech_Payment_Terms__c"/> #><# <Conditional Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c" Match="1" /> #> Chèque<# <EndConditional/> #><# <Conditional Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c" Match="2" /> #> Virement bancaire<# <EndConditional/> #><# <Conditional Select="/SBQQ__Quote__c/SBQQ__Account__r.Payment_Method__c" Match="3" /

I have created action in Dynamic 365 with Get Signatures step. I published that action and it is working fine. When I created one more action with Get Signature step and published. My first action is no longer visible under DocuSign options on record in Dynamics (print screens below). Any suggestions with this issue?Only one action published:Both actions published: 

I’m having issues integrating docusign into my power pages test environment.I was trying the developer account, followed the setup, but can’t enable the e-signature.Am I missing something?Would be grateful if anyone could help :)​​​​

My document has a radio button with four choices.  The signer clicks one of the radio buttons and signs the letter.  That works fine.  I then run Power Automate to save the signed letter in a Shaerpoint folder.  That works fine.  I have another Power Automate flow that reads information from the envelope and creates a record in a Sharepoint list.  This works fine as well.The only thing I can’t do is read values from the fields in the signed document.  I need to add the radio button value to the Sharepoint list together with the other envelope data.  Any ideas?