Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

Making changes to existing forms and fields in Events

Learn the right way to make changes to your existing forms and fields in Events without disrupting data, field mapping, or reporting

If you already have live forms in Events and want to make updates, it’s important to understand how forms, fields, and layouts work together.

 

This article explains how to make changes confidently while taking existing data into account, and links to more detailed guides for each scenario.

 

Before you start

Most questions on your form connect to a field in the Object Manager. This link ensures responses flow correctly into your event records and dashboards.


When you edit a form, consider not only what reporters see but also how your changes may influence the way data is collected and stored.

 

For some updates, such as rewording or moving questions, there’s no effect on your data.


For structural edits, like adding or removing fields, it’s best to plan your changes carefully or test them in a duplicated form first.

 

🔗 For more information on how field mapping works, see this article.

 

Common changes and how to handle them

Here are the most common updates you might want to make to your existing forms, with links to step-by-step articles for each one:

 

✏️ Content and layout updates

These changes affect how the reporting form and Event Record look and feel for users, but don’t change how data is stored.

⚙️ Structural and data-related changes

These changes affect how your form connects to stored data, so it’s best to review their impact before publishing.

 

Best practice when editing forms
  • Plan updates first. Note what you want to change and which fields may be affected.

  • Keep forms simple. Avoid unnecessary questions or options that make reporting harder to manage.

Tip: You can make most text or layout updates directly in your live form. For anything that changes how data is stored or displayed in the Event Record, take a moment to plan or test before publishing.