ZenotiHelp

Relationship Details Component

ZTZenoti Docs Team Updated November 10, 2026 7 min readGuide

The Relationship details component is a form builder component that displays a guest's saved relationships β€” such as family members or emergency contacts β€” directly inside a form. When you add this component to a form, it reads relationship data from the guest's profile and presents it as a table, with one row per relationship, at the moment the form opens.

Audience: Form administrators who design forms using the form builder.


On this page


Before you begin

  • The form must be created using the form builder. The Relationship details component is not available in the legacy form builder or V1 key-value pair forms.

  • The guest whose appointment the form is attached to must have relationships saved on their profile before the form opens. Relationships are managed on the guest profile, not inside the form.

  • You need the following permissions to work with forms:

    Permission: Edit under CustomFields in the Administrator section of the security role β€” required to edit form definitions.

    Permission: Edit under GuestCustomData in the Guest Manager section of the security role β€” required to edit guest form data after submission.

Note: The Relationship details component does not write anything back to the guest profile. You cannot add people to a guest's relationships from inside the form, and the component has no connection to family bookings, group bookings, or creating appointments for the people listed.

Steps

Open the form in the form builder

  1. Navigate to Configuration > Forms.
  2. Locate the form you want to edit and select Edit.
  3. The form opens in the form builder.

Add the Relationship details component

  1. In the component palette on the left, locate the Guest Info group.

  2. Drag the Relationship details component onto the form canvas and drop it in the position where you want the relationship table to appear.

    The component renders immediately as a table with one template row and two columns: Name and Relationship.

    Note: The Name and Relationship columns are locked. You cannot edit their header labels, delete them, reorder them, or reduce the table below two columns. Guests filling the form cannot type over the values in these columns β€” the values are read directly from the guest's profile.

  3. Select Save to save the form.

Verify the component in context

Important: The template row shown in the form builder is a placeholder. When the form opens for a real appointment, the component repeats the row once for each relationship on the guest's profile as of the moment the form opens. If the guest has no relationships on file, the component displays No relationships assigned instead of a table.


How the component behaves at runtime

The Relationship details component behaves differently depending on whether the form has been submitted.

State Behavior
Form not yet opened No data is loaded until the form opens for a specific appointment.
Form open, not submitted The component shows the guest's current relationships. If relationships are added, renamed, or removed on the profile before submission, the form reflects those changes the next time it is opened.
Form submitted The component stores a snapshot of each row at the moment of submission, including the relationship identifier, name, relationship type, and the values of any columns you added. Changes to the guest's profile after submission do not affect the submitted form.
Guest has no relationships The component displays No relationships assigned.

Note: Because submitted forms store a snapshot, a guest who fills the same form again on a later visit will see their current relationships at that time β€” not the relationships from the earlier submission.


Add extra columns to the component

You can add columns beyond the two locked columns to collect additional information about each relationship.

Add a column

  1. With the form open in the form builder, select the edit control on the Relationship details component.
  2. Select the option to add a column.
  3. Configure the new column:
    • Enter a column header label.
    • Choose the field type for the cells in that column. Supported field types include text, radio, checkbox, and dropdown.
    • You can place more than one field inside a single cell.
  4. Repeat for each additional column you need. There is no limit on the number of columns you can add.
  5. Select Save to save the form.

Remove an added column

  1. Select the edit control on the Relationship details component.

  2. Locate the column you want to remove and select the option to remove it.

    Important: You can only remove columns you added. The Name and Relationship columns cannot be removed.

  3. Select Save.

Apply conditional formatting

The Relationship details component supports the same conditional formatting as the standard table component in the form builder. To show or hide an added column based on another field's value:

  1. Select the edit control on the component or on the individual field within an added column.
  2. Open the Conditional settings.
  3. Under Simple, configure the rule:
    • This component should Display β€” set to the display condition.
    • When the form component β€” select the source field.
    • Has the value β€” enter the trigger value.
  4. Select Save.

Note: Values entered in added columns are saved against the relationship record, not against the row's position in the table. If the order of relationships on the guest's profile changes between visits, the saved values remain associated with the correct relationship.


Worked example: A medispa adds a Relationship details component to its intake form. They add one extra column called Emergency contact? using a radio field with options Yes and No. When a guest with two relationships on file opens the form, the table shows two rows β€” one for each relationship β€” with their names and relationship types pre-filled and the Emergency contact? radio buttons blank for the guest to complete. After the guest submits the form, the snapshot records both rows with their radio selections. Six months later, the guest's profile is updated to add a third relationship, but the original submitted form still shows only the two relationships that existed at submission time.


Tips

  • Design the form before adding relationships. Because the Relationship details component reads live profile data, test it by opening the form from an appointment for a guest who already has relationships saved. A guest with no relationships will always see the empty state.
  • Use added columns for consent or clinical notes. The locked columns handle identity; added columns are the right place for information specific to the form's purpose, such as consent checkboxes or contact preference fields.
  • Keep added column labels short. The table expands horizontally as you add columns. Long header labels can make the table difficult to read on smaller screens, including kiosk and mobile surfaces.
  • Conditional formatting applies per field, not per row. If you want a field in an added column to appear only when a certain condition is met, configure the condition on that field. The condition evaluates independently for each row.
  • Deleting the component removes the relationship section entirely. If you no longer need the relationship table on a form, select the remove control on the component. This removes the section from the form definition. Submitted forms that already include relationship data are not affected.

Troubleshooting

The component shows No relationships assigned for every guest.

The guest whose appointment the form is attached to has no relationships saved on their profile. Relationships must be added to the guest profile before the form is opened. The form does not create or manage relationships β€” direct staff to update the guest profile first.

The Name and Relationship columns are greyed out and cannot be edited.

This is expected behavior. These two columns are locked by design and cannot be edited, deleted, or reordered. Only columns you add through the edit control can be modified.

An added column's values are missing on a re-opened form.

If the form has not been submitted, the component shows the guest's current profile relationships each time it opens. Values entered in added columns are only saved permanently when the form is submitted. If the form was closed without submitting, those values are not retained. Encourage guests or staff to submit the form rather than saving as a draft if the added-column data must be preserved.

The relationship table does not appear on the submitted form.

Verify that the form was submitted (not saved as a draft). Draft forms do not store a snapshot. If the form was submitted but the table is missing, check whether the component was present in the form definition at the time of submission β€” if the component was added after the form was submitted, earlier submissions will not include it.

Conditional formatting on an added column is not triggering.

Confirm that the trigger value in the Has the value field matches the source field's value exactly, including capitalization. The conditional rule is case-sensitive. Also verify that the source field is on the same form and is not hidden from the guest by a separate visibility setting.


Was this article helpful?
Your feedback helps us improve our documentation.