Back to Docusign.com
Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of April 2025.
Thread: Multiple documents with Auto-Place not using DocumentId
Summary: The developer has created an envelope through the C# SDK and is trying to add tabs to the documents in that envelope using anchor tagging. They have the same anchor string appearing in multiple documents, but they don’t want the same tab to appear in both documents; so they are trying to use the DocumentId property on the tab to resolve this. They are finding that the same tab is still appearing in both documents where the anchor string appears.
Answer: The DocumentId property is only meant to be used when placing tabs with fixed positioning. When using anchor tagging, the tab will appear in every location where the anchor string appears, in all documents in the envelope. To solve this, the developer will need to use unique anchor strings in each document so that each tab only appears once.
Thread: Best way to extract specific document from envelope
Summary: The developer is using the eSignature REST API to construct envelopes with composite templates. They are trying to understand the best approach for downloading a specific document from a completed envelope, given the constraint that, when using composite templates, the values of document IDs don’t stay consistent between the envelope definition and the envelope object itself.
Answer: The suggested approach for identifying documents by something other than the document ID is to attach custom fields to documents with the EnvelopeDocumentFields object. However, in this developer’s case, they are adding documents to the envelope through a server template, so they do not have the opportunity to add an EnvelopeDocumentFields object. For this reason, the developer will need to call the EnvelopeTemplates: list endpoint after creating the envelope, and the response of that API call will include the document ID.
Thread: Docusign envelope distinguishing between Number vs Numerical types in template
Summary: The developer is using a template defined in the Docusign UI that includes various tab types. When they try to set the tab values in the template, they are not seeing the number tabs populate on the envelope.
Answer: The number tabs are not populating on the envelope because they are actually not number tabs, they are numerical tabs. Number tabs are a legacy tab type, and today, templates are created with numerical tabs instead. The following code snippet demonstrates how to set the value of a numerical tab.
"numericalTabs": T
{
"pageNumber": "1",
"documentID": "1",
"xPosition": "210",
"yPosition": "235",
"height": "20",
"width": "70",
"minNumericalValue": "0",
"maxNumericalValue": "1000000",
"validationType": "Currency",
"bold": "true",
"font": "helvetica",
"fontSize": "size11",
"tabId": "salary",
"tabLabel": "Salary",
"numericalValue": "123000",
"localePolicy": {
"cultureName": "en-US",
"currencyCode": "usd",
"currencyPositiveFormat": "csym_1_comma_234_comma_567_period_89",
"currencyNegativeFormat": "minus_csym_1_comma_234_comma_567_period_89",
"useLongCurrencyFormat": "true"
}
}
]