Loading

Nonprofit Success Pack (NPSP): Custom Fields Not Visible on Gift Entry, Lightning Pages, or Opportunity

Publiceringsdatum: Jul 15, 2026
Beskrivning

You added a custom field (such as Type, batch number, or a Contact lookup) to a Nonprofit Success Pack (NPSP) object, but it does not appear where you expect it. This usually happens because NPSP surfaces vary from standard page layouts and require the field to be added to the Gift Entry template, the Lightning App Builder assignment, field sets, or specific field-level security settings.

 

Users often describe this issue as fields being "inaccessible" or "not showing up," even though they exist and have no missing values. The intent of this article is to resolve field-visibility and configuration gaps.

 

Common Symptoms:

  • A field like Type cannot be included on a donation record.

  • A section added in Lightning App Builder shows in the builder but not for end users.

  • A batch number added to an Opportunity does not appear after new batches are added.

  • A Contact lookup added to a donation form does not surface the relationship in the Contact related list.

  • Fields are inaccessible from within the Volunteer Campaign wizard.

  • The Gift Entry error Secure Query Included Inaccessible Field is triggered when adding a Contact or Account.

Lösning

Identify which surface the field is missing from, then follow the matching cause and steps below to resolve the issue.

Cause 1: Field does not appear on the NPSP Gift Entry form

Gift Entry reads from a Gift Entry Template and field set, not the standard page layout.

  1. Navigate to Setup > Object Manager > Opportunity > Fields & Relationships.

  2. Open your field, click Set Field-Level Security, and ensure Visible is checked for every profile that uses Gift Entry.

  3. Go to NPSP Settings > System Tools > Advanced Mapping, then open Gift Entry (or use App Launcher > Gift Entry Templates).

  4. Edit your template, drag the field from Available Fields into the Form Fields section, and click Save.

  5. Note: If you see the error Secure Query Included Inaccessible Field when adding a Contact or Account, confirm the org is on NPSP version 3.201 or later (NPSP Settings > About) and grant Read access to the referenced field via field-level security.

Cause 2: A section or note added in Lightning App Builder shows in the builder but not for users

  1. Open Setup > Object Manager > select the object (for example, Account or Contact) > Lightning Record Pages.

  2. Open the affected page you edited and click Activation.

  3. Set the page as Org Default, or assign it by App and Record Type on the Assign as Org Default / App Default tabs, then click Save.

  4. Note: If the section shows on a Household Contact but not on the Organization/Business Account, the two record types are using different Lightning pages. Repeat the activation process for the Business Account record-type assignment.

Cause 3: A batch number does not appear on the Opportunity after new batches are added

NPSP Data Import batch numbers populate only when the batch is processed, not when records are initially added.

  1. Go to your NPSP Data Import Batch, run Dry Run to validate, then click Process Batch.

  2. Confirm the field is on the Opportunity page layout by navigating to Setup > Object Manager > Opportunity > Page Layouts.

  3. Drag the field onto the layout and click Save.

  4. Confirm field-level security Visible is checked (as outlined in Cause 1, Step 2).

Cause 4: Fields are inaccessible inside the Volunteer Campaign wizard

Wizard-driven screens read from packaged field sets, not the page layout.

  1. Confirm field-level security Visible is checked for the running user.

  2. Add the field to the wizard's field set by navigating to Setup > Object Manager > select the object > Field Sets.

Knowledge-artikelnummer

005389017

 
Laddar
Salesforce Help | Article