function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
CRichmanCRichman 

Unexpected Error

Hi, I am not able to solve this through SF support so I am really hoping that someone here can tell me were to begin fixing this issue.

 

 Standard users are not able to resave an opportunity(any record type) after updating. They receive the following error.

Opportunity Edit

Error: Invalid Data.
Review all error messages below to correct your data.
Apex trigger npe03.Donations caused an unexpected exception, contact your administrator: npe03.Donations: execution of AfterUpdate caused by: System.QueryException: sObject type 'npe03__Recurring_Donation__c' is not supported.: (npe03)

 

As System admin, I am able to resave on update with no problems, so I'm assuming it's a security/permission error?, but I am unable to find the issue triggering this error.

We have the following packages installed in our Non profit instance.

Recurring Donations Salesforce.com Foundation 2.0.12
Relationships Salesforce.com Foundation 2.0.1
Affiliations Salesforce.com Foundation 1.55
Contacts & Organizations salesforce.com Foundation 2.1.4
Households Salesforce.com Foundation 2.4.7

 

 

 

ForceComForceCom

Hi, 

 

Can you check the permission given on the profile for this package components. 

 

You might have installed the package with default permissions, as "Grant access to all admins". This is the reason , you are able to save everything but not the other users. 

 

Check the permissions on the profile.

 

Thanks,

Dharani

 

CRichmanCRichman

All users have View all and Modify all permissions on Recurring Donations, which is the package referenced in the error. However the opportunities that are being modified are not recurring donations.

vbsvbs
@CRichman - You need to verify access permissions specifically for the object mentioned in the error - npe03__Recurring_Donation__c.
PeterMosherPeterMosher
Is this error caused by a managed package or one of your apex scripts?

If it was caused by a managed package I would contact the company that makes the package in question.

If it was caused by a script you wrote do this:
Run the Developer Console, cause the error and go back to the Developer Console. If it is caused by your code it should have a line number there for you in the logs, one of them will have Error, scroll down to the bottom and it will give you a stack trace.