@KhaleelullaSK 

The Docusign Demo (Preview) Connector is connecting to a Docusign demo account for testing and development, while the Docusign Main Connector is connecting to production for real transactions. The functionality is the same, it is just pointing to different server environment in the background.

No, you need to establish a connection to for both Connectors, as the accounts are on different server environments without a connection between the data centres. Also all the related IDs, like account Id, user Id, template Id, etc. will be different and you cannot mix and match between the two environments.

​Hi @KhaleelullaSK,

I hope you are doing well.

I would like to confirm if you were able to solve your issue by utilizing the solution that was suggested?           

If so, please mark it as the best answer by clicking “Select as Best” to make it easier for other users to find. Otherwise, feel free to let me know and I will gladly help you address the situation as soon as possible.

Best regards,   

Alejandro R. | Docusign Community Moderator   

"Select as Best" below if you find the answer a valid solution to your issue!   

​

The way the connector is built in Power Automate is really flawed. You can't set up a process where you test your flow in a test environment and then easily push it to production, because the test and production environments require two completely different connectors.

You can’t just build a complex flow for testing and then duplicate it by manually replacing every single DocuSign action with the production version, and then when a change occur you have to properly edit both flows.

I honestly don’t know how this is supposed to work. Testing directly in production doesn’t seem right due to cost concerns, but I don’t see any other viable alternative

The use of separate connectors for prod and demo is not going to work for any solutions deploying between environments.  When you deploy to test or prod environments you do it as a managed solution so that it is completely read-only, with any changes being via the use of Environment Variables or different service accounts.

If there is no way to use a demo account via the normal Docusign connector, then docusign need to get rid of the demo connector completely and just have a dropdown within the connector to choose if it connects to the demo or prod environment. This could then be set via an environment variable for deployment.

The only option for now seems to be for us to build a Custom Connector   

Hi @dji, and @Jim169,

 
Thank you for following up. 

This behavior is a reflection of our application’s server infrastructure, due to this reason there is no way to work around it with its current design. Nevertheless, feedback that can improve our users’ experience is always welcome. I encourage you to consider submitting your idea to be reviewed by our development team for possible implementation. If you’re a Docusign Administrator for a corporate plan, you have the additional option of filing your request through a support case, or by reaching out to your Account Team. Otherwise, we invite you to share your product suggestions and feature requests on our dedicated ideas page (https://community.docusign.com/ideas), where we can collaborate to shape the future of our product together.

Feel free to let us know if you need further assistance with this. 

Best regards,  

Alejandro R. | Docusign Community Moderator  

"Select as Best" below if you find the answer a valid solution to your issue!  

I’ve created a product suggestion for this