Salesforce Nonprofit Cloud: Custom Field Missing in Guided Wizard or Unable to Rename Preset Field

Cause 1: Custom field on the page layout does not appear in a guided wizard

Root Cause: Unlike standard Salesforce pages, Nonprofit Cloud guided wizards and intake flows render fields from either a Field Set or an OmniScript form definition, rather than the standard page layout.

Step-by-Step Fix:

1. Check if a Field Set controls the wizard:

   • Go to Setup > Object Manager and select the object.

   • Click Field Sets.

   • If a field set is used by your wizard, click edit, drag your custom field from the palette into the In the Field Set container, and click Save.

2. Check if an OmniScript or Flow controls the wizard:

   • Go to Setup > OmniStudio (or Setup > Flows depending on your implementation).

   • Open the active OmniScript or Flow associated with your guided intake.

   • Locate the step/form element where the field should reside.

   • Add a new input element and bind it to your custom field's API name (e.g., Custom_Field__c).

   • Save, activate the new version, and deploy.

3. Align Page Layouts and Security:

   • Go to Setup > Object Manager > [Your Object] > Page Layouts. Ensure the field is on the page layout so users can view/edit it on the record detail page after completing the wizard.

   • Navigate to Fields & Relationships > [Your Field] > Set Field-Level Security and ensure the running user’s profile is set to Visible.

Cause 2: Salesforce-managed preset field cannot be renamed

Root Cause: Preset fields are managed by the Salesforce package and their labels are locked. To change the terminology, you must create a replacement custom field and migrate existing records.

Step-by-Step Fix:

1. Create the Replacement Field:

   • Go to Setup > Object Manager > Proposal (or target object) > Fields & Relationships > New.

   • Choose the matching data type.

   • Set the label to your preferred term and name it. Click Save.

   • Set Field-Level Security to ensure relevant profiles have Visible checked, then add it to your Page Layouts.

2. Migrate Existing Data (Via Data Loader):

   ⚠️ Note on Known Issues: Do not use the standard Data Import Wizard for this migration. Known issue KI-01883 can cause mapping errors, and KI-30616 prevents bulk record type assignment. Use Data Loader instead.

   • Run a Salesforce report or use Setup > Data Export to extract the record IDs and the values from the old managed field (e.g., Request Amount).

   • Open Data Loader and select Update.

   • Map the extracted IDs and the old field values to your new custom field API name.

   • Run the update and verify that the values have successfully copied over on a few test records.

3. Alternative Migration (Via Record-Triggered Flow):

   • If you prefer to migrate via platform tools, build a record-triggered Flow on the object.

   • Configure it to run on create/update to copy values from the managed field to your new custom field.

   • Run a one-time scheduled path/batch flow to populate historical records.

4. Clean Up:

   • Once data integrity is verified, remove the original managed field from all page layouts to prevent double-entry. Do not attempt to delete the managed field, as it is packaged and required by system integrity.

Validation

• For Wizard Visibility: Run through the guided intake process as an end-user. Confirm the new field displays, accepts input, and writes successfully to the database.

• For Data Migration: Open several migrated records and confirm that the new custom field contains the exact historical value previously stored in the managed preset field.