Skip to main content

Forms Troubleshooting: Red Error Banner in the Form Editor

Jessica Lara
  • Updated

This article covers the red error banner that can appear at the top of the page when you edit a form in the Advanced Form Editor. The banner always describes the specific error in its message. This article explains how to read it, the most common causes you can fix yourself, and when to contact Support.

💡Quick Answers

  • What does the red banner at the top of the form editor mean? There is an error on the page, and the banner describes the specific problem in its message. Read the message, fix what it names, and save again.
  • Where does the banner appear? At the top of the page in the Advanced Form Editor, usually after you try to save.
  • My changes aren't taking effect. The Advanced Form Editor requires a manual save, so make sure you are saving your changes before exiting the page. If you are unable to save, check the top of the page for a red banner with a list of errors.
  • When should I contact Support instead? When the change touches dependencies, Liquid logic, business rules, or an integration, or when you cannot resolve the banner message yourself.
  • Who can edit forms? System Admins and Admins (with any permission), in the Settings > Forms menu.

In this Article

What the Banner Means

A red banner at the top of the Advanced Form Editor means there is an error on the page. The banner always describes the specific error in its message, so the exact wording depends on what went wrong. Start by reading the message, then match it to one of the common causes below.

Red Error Banner on Form.png

Read the Error Message

  • The banner appears at the top of the page in the Advanced Form Editor, usually after you try to save.
  • The message text names the specific problem, entity, page, field, and field value (if applicable). Note the exact wording; you will need it if you contact Support.
  • Fix what the message points to, then save again to confirm the banner clears. If you are unsure how to proceed, submit a request to Support.

Common Causes You Can Fix

Here are some common editor errors that you may encounter:

  • Dependency option has been removed: If a field option being used as a dependency on a form is removed from the field on the Fields page, you will see an error on the form. Either update the dependency by selecting a new option or remove the dependency completely.
  • Duplicate fields mapped to the same entity: A field can be mapped to each entity once on the form. For example, you can have multiple Name fields, but only one can be mapped to the CHILD, one to PARENT 1, etc. Delete the duplicate field or map to a different entity that has not been used.
  • A tracking code or script added to the form: Adding tracking codes or scripts to a form through a hidden field is no longer supported and can trigger a banner error. If you need to edit one, remove the hidden field from the form and move the script to a Custom HTML template instead. See "Use Custom HTML to Add Tracking Codes/Scripts to Parent Portal Thank You Pages."
  • A required setting on a new field is blank: When you add a field to a form, the Prompt and Map To settings are required. If either is left blank, the editor returns an error when you save. Open the field, enter the Prompt text families will see, and set Map To (usually CHILD), then save again. See "Forms DIY: Add a question or prompt to a form (adding fields)."

Save, Preview, and Publish

  • Save your changes in the Advanced Form Editor.
  • Preview the form. Switch to the Basic Editor to preview the change and make simple text edits (these save automatically) or click Select > Preview.
  • Publish the form (Select > Publish (Make Active)). Changes are only live once published.

When to Contact Support

Some changes can break silently if a downstream connection is not accounted for. Consult Support before or when:

  • The change touches dependencies, Liquid logic, business rules, or an integration.
  • You are editing a recommendation form or contract during peak seasons.
  • You cannot resolve the banner message on your own.

Submit a request to Finalsite Support and include:

  • The exact banner message. Copy and paste or screenshot the message.
  • The form. The form name and whether you are in a draft.
  • What you were editing. The field or element you were adding or changing when the banner appeared.
  • The change type. Whether it involves a dependency, filter, Liquid, etc.

Additional Resources

Related articles

Comments

0 comments

Article is closed for comments.