Skip to main content
New Voice
August 10, 2026
Question

Public integration Go-Live — Partner Program application form fails with Apex error

  • August 10, 2026
  • 4 replies
  • 55 views

We have a public integration built and tested in the demo environment. Each user connects their own Docusign account via OAuth; envelopes are sent from and billed to the users' own accounts. We are not reselling or embedding Docusign.

We cannot submit the Partner Program application. The form at partners.docusign.com/s/join-now fails every time with "Failed to Insert record — List has no rows for assignment to SObject". Latest attempt: 2026-08-10, English-only ASCII input, corporate email domain, clean incognito session with extensions disabled. No field-level error is shown, so this appears to be an uncaught QueryException rather than a validation error.

Question:Is there an alternative way to submit the application, or could a Partner Onboarding rep set us up directly? I can provide the exact submission timestamp and email address for the Apex debug log.

4 replies

Docusign Employee
August 11, 2026

Hello Cecilia,

Thank you for reaching out and for the detailed description of what you tried when submitting the partner application via https://partners.docusign.com/s/join-now on 10 August 2026.

We have been able to confirm that the message you are seeing ("Failed to Insert record — List has no rows for assignment to SObject") is coming from the backend system that processes partner applications, rather than from anything in your browser or in the specific values you entered. This error is thrown when the form submission reaches a Salesforce path where a required configuration record or email template is missing, which means the system is raising an internal exception instead of returning a clear validation message to you.

One known scenario that can trigger this behaviour is when an application is submitted from a country that is currently on our restricted-country list for the partner program. In that case the application should be cleanly rejected with a specific message and notification, but at the moment an internal error is raised instead. Your report strongly suggests you are hitting this same class of issue.

How we can move your application forward While the fix is in progress, we do not want this error to block you. If you are comfortable, please open a Support ticket and share the following details so I can route your application manually to our Partner Onboarding team:

  • Legal company name and primary website

  • Country/region and primary operating geography

  • Which partner motion you are interested in (for example: Independent Software Vendor (ISV), System Integrator, or Reseller)

  • A brief description of how you intend to use or integrate with Docusign

  • The email address you would like us to use as the primary contact for the partnership

  • (Optional) Your existing Docusign account ID, if you already use Docusign today

Once I have this information, I will share it internally with the Partner Onboarding team so they can create or complete your application on your behalf and follow up with next steps.

Again, I apologise for the poor experience here and appreciate you flagging the issue with such clear detail. Please let me know if you have any questions or if you see the behaviour change on a future attempt.

Regards,

Marwan Badreldin

Developer Support Engineer II, Docusign

New Voice
August 13, 2026

Thank you — this is very helpful, and it matches our own read of the error.

Here are the details you requested:

1. Legal company name and primary website:
    ***PII removed***
   ***PII removed***

2. Country/region and primary operating geography:
   Incorporated in Shanghai, China. Primary operating geography is the
   United States — our users are US-based venture investors and startup
   founders, and our infrastructure and data residency are in the US.

3. Partner motion:
   Independent Software Vendor (ISV). We are not reselling or embedding
   Docusign.

4. How we intend to integrate:
   A public integration (Authorization Code Grant with PKCE). Each user
   connects their own Docusign account via OAuth to execute NDAs and SAFE
   agreements with their matched counterparty. All envelopes are sent from
   and billed to the users' own Docusign accounts; nothing is billed to us.

5. Primary contact email: ***PII removed***

6. Existing Docusign account ID:
  ***PII removed***

Two questions, and I would appreciate a direct answer to both even if the
answer is unfavourable — it will save us both time:

a) Is mainland China currently on the restricted-country list for the Partner
   Program? If our application will ultimately be rejected on that basis, I
   would rather know now than proceed through App Review.

b) If mainland China is restricted: would an entity incorporated in a
   non-restricted jurisdiction (for example United States) be
   eligible? And in that case, could our existing Integration Key
 ) be transferred to the new entity,
   or would we need to rebuild the integration under a new key?

c) Separately: do the Partner Program requirements of "one year in business"
   and "20 employees" apply to our case? We are a small company.

Docusign Employee
August 14, 2026

Hello Cecilia,


Thanks for your kind response, Kindly open a Support case with the required information.

 

Regards,

Marwan Badreldin

Developer Support Engineer II, Docusign

New Voice
August 18, 2026

Thanks Marwan. I ran into a blocker trying to follow that: our account is a free developer account (Account ID 49480797) with no production plan, and per Docusign's own policy, free support plan customers — including developers who have a developer account but have not yet purchased a production account — cannot create support cases and must use self-service channels only.

The Partner Portal route requires Partner credentials, which is exactly what we are trying to obtain. And the join-now form fails with the backend Apex error your colleague already confirmed.

So all three intake channels are currently closed to us. Could you either open the case on our behalf, or route our details internally to the Partner Onboarding team?

I have everything ready — legal entity name and website, country and operating geography, partner motion (ISV), integration design, primary contact email, and our Integration Key — plus three eligibility questions, including whether mainland China is on the restricted-country list for the Partner Program. Happy to send it wherever you prefer, or by email if that's easier.     

I still got two questions, and I would appreciate a direct answer to both even if the
answer is unfavourable — it will save us both time:

a) Is mainland China currently on the restricted-country list for the Partner
   Program? If our application will ultimately be rejected on that basis, I
   would rather know now than proceed through App Review.

b) If mainland China is restricted: would an entity incorporated in a
   non-restricted jurisdiction (for example United States) be
   eligible? And in that case, could our existing Integration Key be transferred to the new entity,
   or would we need to rebuild the integration under a new key?