DocuSign number validation fields

Hi @ColinH 

Might be best to open a ticket with Zapier Support for further assistance: https://zapier.com/app/get-help

You can try using a different esign app, such as PandaDoc: https://zapier.com/apps/pandadoc/integrations

Thanks, Troy. I went ahead an opened a ticket with Zapier Support as well.

In terms of using a switching from DocuSign to PandaDoc, or another esign app, that’s a pretty significant workflow change to accommodate a relatively simple issue.

@ColinH 

Keep in mind that if this is indeed a bug there’s no guarantee it will get fixed any time soon, since most apps on Zapier are built and maintained by the app developers themselves, and Zapier keeps an internal list of app requests.

@Troy Tessalone Well I tried exploring PandaDoc, according to this, they don’t have a date field that is auto populated based on when the document is signed. That’s a requirement for us, because the contract dates and timeline are variable fields based on when the contract is signed.

@ColinH

Internally the timestamp for when a document was signed is stored and can be made available via Zaps.

I think we’d need a better understanding of how you are trying to use that variable, perhaps with a specific example.

PandaDoc has these available triggers:

Hi there, @ColinH!

Thanks for reaching out! I did some digging and it appears custom fields for the Create Signature action don’t support numbers at the moment.

That said, we do have a feature request open to add support for this. I've gone ahead and added your vote! While I don’t have a timeline to offer on when or if this will get implemented we’ll be sure to keep you and the thread updated if it does. 🙂

Thanks again for sharing your thoughtful feedback!

Hi @christina.d, Thanks for your response! I saw that not as well, however, this isn’t a custom field. It’s a regular text box field with numerical validation. Not sure if that changes anything.

Thanks for clarifying that, @ColinH! 

Hmm, it sounds like the the number validation that is being applied to the text field is definitely causing issues with us being able to load the field correctly in the Zap. I think it could well be a bug that you’re running into here. I can see that you’ve got a conversation going on with our Support team about this which is great. They’ll be able to open up a bug report for this to investigated further. 

In the meantime, can you try turning off the field validation so that the fields appear and finish setting up the Zap? Then, if you turn the Zap on and re-add the field validation and the Zap runs does it run into any errors? Or do the fields with validation not get updated as expected?

I’m hoping that as we’re able to load the fields initially, the Zap may still be able to send data to them once the validation is in place. 

Thanks so much for looping back to share your workaround, @ColinH!