Custom Field Errors

When you add or configure custom fields, issues usually occur because of how the field is set up in Settings or how it behaves on the record. Use these guidelines to identify and resolve common errors.

Cause

The custom field does not exist in Settings, or it exists under a different type.

Resolution

  • Confirm the field exists in Settings, Custom fields.

  • Verify the field type matches the form:

  • Constituent forms require a constituent custom field.

  • Donation forms require a gift custom field.

Cause

A custom field can appear only one time on a form.

Resolution

  • Use the field once on the form.

  • If you need to collect similar information multiple times, create separate custom fields.

Cause

The field is configured to allow only one value per record.

Resolution

  • Review the field configuration in Settings.

  • If you need to keep multiple responses, update the field settings to allow more than one value.

  • Inform users that submitting a new value replaces the existing value when the field allows only one entry.

Cause

Yes/No fields default to No when left unchecked.

Resolution

  • Make the field required if a response is needed.

  • Update the field label or help text to clarify expectations for users.

Cause

A custom field is set to require a response, but no value is provided.

Resolution

  • Provide a value for the required field before saving.

  • Remove the requirement if the field should be optional.

Cause

The field label on the form differs from the field name in Settings, or the field is used for a different purpose than intended.

Resolution

  • Review and update the Custom field label on the form.

  • Confirm the field selected matches the data you want to collect.

  • Use clear, descriptive labels to help users understand what to enter.