Open camilopulidoms opened 3 months ago
Hello,
I don’t see any issues with your code; however, it seems there is a mismatch of recipient details between the create envelope call and the recipient view call. The create_recipient_view method will return a URL with the signer field option only if the recipient is a signer, providing the signing ceremony.
Could you please raise a support case and provide the API logs [https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=jux1643235969954&topicId=poz1578456669909.html&_LANG=enus] for further troubleshooting?
To verify with the code, please find the links below: https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-in-app-embedded/ https://github.com/docusign/code-examples-python/blob/master/app/eSignature/examples/eg016_set_tab_values.py https://www.docusign.com/blog/developers/deep-dive-the-embedded-signing-recipient-view
Thankyou.
I'm encountering an issue with the create_recipient_view method in the eSignature examples. My goal is to use this method to allow users to sign documents via a web-view. Here's the relevant code snippet I'm using:
The issue I'm facing is that the generated URL returns a PDF document without the option to sign, and the fields that should be automatically populated remain empty.
I want to emphasize that my email flow works correctly: it generates an envelope with dynamically filled fields and provides the signing options. The problem only arises when using the create_recipient_view method.
Is there something I'm missing in the RecipientViewRequest configuration? Any help or guidance would be greatly appreciated.
Thank you!