This article explains why a Nonprofit Cloud Fundraising user may receive a permission error when clicking the New or Edit Gift Entry button, or when running the Manage Gift Commitment Schedules invocable action, after you have already corrected field-level security.
Users see errors such as "You do not have permission to modify npe__Recurring_Donation__c/npe__Recurring_Donation_Campaign__c" or "[user] doesn't have access to [field]" where the message references fields like ObjectSourceCodeId or PaymentInstrumentId but does not state which object those fields belong to. The New and Edit buttons fail while the pencil-edit on an existing Gift Entry field may still work.
This affects non-administrator profiles and permission sets that have object-level Edit but incomplete field-level security across the full set of related Fundraising objects (GiftTransaction, GiftTransactionDesignation, GiftCommitment, GiftCommitmentSchedule, GiftSoftCredit, GiftDesignation).
The user is missing field-level security on a related Fundraising object the error does not name.
1. Identify the exact field and object. The Gift Entry error names a field (for example ObjectSourceCodeId or PaymentInstrumentId) but not its object. Check field permissions on ALL related Fundraising objects, not only the one on the form: [GiftTransaction], [GiftTransactionDesignation], [GiftCommitment], [GiftCommitmentSchedule], [GiftSoftCredit], and [GiftDesignation].
2. Go to Setup > Object Manager > select each object above > Fields & Relationships > select the named field > Set Field-Level Security.
3. For the user's profile or permission set, select Visible and clear Read-Only so the field is editable.
4. Repeat for the same field on every related object listed in step 1 until you find and grant the object where it was missing.
005389035

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.