Create unmapped fields for registration forms (preview)

[This article is prerelease documentation and is subject to change.]

Custom unmapped fields (also known as custom registration fields) allow you to create and manage personalized questions for event attendees without affecting the Lead or Contact entity. Custom unmapped fields allow you to collect relevant information for each event, such as dietary preferences, session interests, feedback, and more. You can use the information gathered to customize the communication with your attendees and personalize the event attendee experience.

Tip

This article describes custom unmapped fields for event registration forms. For information on custom unmapped fields in marketing forms, see Create unmapped fields for marketing forms.

Important

• This is a preview feature.
• Preview features aren’t meant for production use and might have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.

Creating unmapped form fields for your event

To create a custom unmapped form field for your event, navigate to the Event planning > Form tab. You can now see a preview of the form on the right side by selecting the Edit button. Once selected, you're taken to the form editor. Select Edit to edit the form.

If this form is used in multiple events, you're presented with a dialog. You have the following two options:

• To edit the form for all events that are using this form, click the provided link. This opens the reusable form in the Forms section.
• To edit the form for this event only, select Create a copy.

In the form editor, you'll notice a new section called Unmapped where you can select previously saved fields or select + New to create a new field.

Creating a new unmapped form field

In the form editor, you can drag and drop a field type from the Elements panel to create unmapped fields of the corresponding type.

Each unmapped field has a logical field name. There can be multiple fields with the same logical field name, but you can only use a field of the same name once in a form. Once you add a field to the canvas, all fields with the same logical name are disabled in the right pane and can't be added to the form. The logical field name is used as the key for the submitted value and it's also used in journey orchestration based on the submitted values of the unmapped field. You can define the field label, placeholder text, default value, and set if the unmapped field is required for submission. You can hide the unmapped field, and set up a custom validation of the submitted value.

The following field types are available for creating unmapped fields:

• Short text: A field for standard input.
• Long text: A field for longer text inputs.
• Option set: A field for multiple option selections. You can select if the field is displayed as a dropdown or radio button. The user submitting the form can only select a single value.
• Multi-select: A field rendered as a list of checkboxes. You can create multiple options. The user submitting the form can select multiple values.
• Radio button: A field limited to only two options.
• Number: A field that only accepts numeric values inputs.
• Checkbox: A field containing a single checkbox.
• Date & time: A field for inputting a date. You can configure the field for date only or for both date & time.

Save fields to reuse them in other forms

Unmapped fields and modified mapped fields can be saved for later reuse in other forms. The saved fields are shared across your organization, allowing your colleagues to use fields you've created.

The saved unmapped fields are listed in the Unmapped section of the Fields right side pane.

Once you add a saved field to canvas and modify it, you can save the changes to the original saved field by selecting the Update field button.

The display name of the saved field must be unique. If you enter the same display name of an existing field, you'll be asked if you want to overwrite the existing field.

Viewing submitted responses

Responses to the custom unmapped fields are recorded in the form submission response. Navigate to Registration and attendance to view all responses and event registration information in one table. Information includes the contact's registration ID, name, email, registration status, and date of creation. This joint data table is created as a new system view for the registration form.

Note

It can take up to two minutes for the new system view to be created after a first submission is received.

You can also create a new system view that can be reused across all events. To construct advanced queries, advanced search should be enabled for your organization. For more information, see Advanced find in model-driven apps.