Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

cannot read 'recipientWrappers' of null error

New Here ,
Mar 01, 2017 Mar 01, 2017

Using AdobeSign for SFDC and selecting a "user" record type as a recipient.

Everything is working great except when I use one particular user I get this error:

Error in $A.getcallback() [Cannot read property 'recipientWrappers' of null]  Callback failed: apex//echosign_dev1.AgreementComponentController/ACTION$loadaAgreement failing descriptor: {markup://echosign_dev1:AgreementEditor}

I have checked EVERYTHING on this particular user's record compared to other users that work with this agreement.

I have changed user to a SFDC user with same profile and role in SFDC and agreement works fine.

I have to be missing something, but I cannot figure this out.

Has anyone else ever encountered this problem?

2.6K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 09, 2017 Dec 09, 2017

Hi mattlandr,

Wondering if you have had any luck in resolving this issue, or at least know of the cause for this issue?

Kind Regards,

william

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 06, 2020 Apr 06, 2020

Hi, Just resolved this in my org.

 

Check if you have a sharing rule limitation on User object. Open it up, that worked for me.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 07, 2020 Apr 07, 2020

Update: You also need to give a sharing rule for the contact. If Contact is controlled by parent, you have to share the accounts.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 28, 2022 Jul 28, 2022
LATEST

Hello, what solves this for me is going to the contact record in SalesForce and making sure there are no symbols in ANY of the phone fields other than spaces or dashes. Check all phone, mobile and fax fields. Remove any plus signs, +, parathensis, etc. Solves it every time. Don't know why these symbols in the phone field disrupt the integration for sending a document via email, but there you go. 😉 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines