Skip to main content
Solved

Use custom fields in email subject and body in Bulk Sent

  • January 21, 2025
  • 5 replies
  • 93 views

Forum|alt.badge.img+2

Hi guys!

I need to use a Custom Field in my envolpe in both the subject and the body of my email through bulk sent. Tried many of the solutions in this community but none of them could solve this issue. Here is the steps I followed:

  • Created a custom field in my account;
  • Used this custom field in the template I'm using;
  • Filled the example CSC with the values I need for the custom field;

However, in the email subject, the custom field is not appearing in the drop down box and I've tried a lot of formats to include the custom field but none of them worked properly. ([[ECF:CustomField]], [[CustomField]], [[CustomField]])

Perhaps I'm still missing a few steps in this setup… 

Could anyone help me with this issue? I've just read of threads here and couldn't manage to solve this.

Best answer by mrave

@samuel_ayres 

Correct, you need to be a Docusign eSignature Admin to set up an account wide Envelope Custom Field. If you don’t have the necessary permissions, you may reach out to the Docusign Admin in your company.

If you are allowed to create templates, another option would be for you to create a free developer account, where you will be Admin. Then you can create the ECF there and add it to a template, which you can then export and import into your production account, if you have the template permissions, you should be able to.

View Original
Is this content helpful?

5 replies

Michael.Rave
Docusign Employee
Forum|alt.badge.img+14
  • Docusign Employee
  • 935 replies
  • January 21, 2025

@samuel_ayres 

The correct syntax to use in the email subject is [[ECF:ECF field name]].

For an envelope custom field called “Agreement Type”, the correct syntax is [[ECF:Agreement Type]]

This only works for envelope custom fields (metadata of the envelope) and not document custom fields (fields of the documents). These two different field types are sometimes confused with one another.


Forum|alt.badge.img+2
  • Author
  • Newcomer
  • 2 replies
  • January 21, 2025

Hi ​@Michael.Rave ,

 

Thanks for your answer. I guess the main problem here is that I need to have an Admin permission in order to create an Envelope Custom Field. When I did the First Step I mentioned (Created a custom field in my account), I actually created a Custom Field but not an Envelope Custom Field. Therefore, I couldn't use the ECF syntax in the e-mail subject. 

 

 


Michael.Rave
Docusign Employee
Forum|alt.badge.img+14
  • Docusign Employee
  • 935 replies
  • Answer
  • January 22, 2025

@samuel_ayres 

Correct, you need to be a Docusign eSignature Admin to set up an account wide Envelope Custom Field. If you don’t have the necessary permissions, you may reach out to the Docusign Admin in your company.

If you are allowed to create templates, another option would be for you to create a free developer account, where you will be Admin. Then you can create the ECF there and add it to a template, which you can then export and import into your production account, if you have the template permissions, you should be able to.


Forum|alt.badge.img+2
  • Author
  • Newcomer
  • 2 replies
  • January 22, 2025

I asked the Docusign Admin in my company to create the ECF and then I was able to add it in the E-mail subject. Issue solved!

I will also try the other option you provided ​@Michael.Rave , I think it could be useful in some situations.


Michael.Rave
Docusign Employee
Forum|alt.badge.img+14
  • Docusign Employee
  • 935 replies
  • January 22, 2025

@samuel_ayres 

Great to hear you were able to resolve the issue.

Yes, the advance of the template approach is that this ECF will only be present on that template and not show up for all users, opposed to it being added via the Admin, which adds it for every user and send.


Reply