---
title: 4. Dynamic Edit Forms
slug: docs/4-dynamic-edit-forms
docTags: 
createdAt: 2026-06-08T08:15:45.970Z
---

Double-clicking a field or object in the schema tree auto-generates a form pre-populated with the profile's current values. All editable fields can be modified for your demo scenario.

## How forms are generated

1. Trigger — double-click on a schema node When you double-click a field or object in the left schema tree, the right panel renders a dynamic form scoped to that node and its children.
2. Pre-fill from live profile Every input is populated with the current value from the AEP profile store, so you only need to change the fields relevant to your use case.
3. Input type inferenceThe form renders the correct control based on the XDM field type.
4. Changes tracked in memory All edits are held in a local change set. Multiple forms from different schema nodes can be edited in one session — all changes are collated when you clickUpdate profile.

### Input type mapping

| XDM type          | Form control                  |
| ----------------- | ----------------------------- |
| String            | Text input                    |
| Boolean           | Checkbox (e.g. consent flags) |
| Date-time         | Date picker                   |
| Integer / Decimal | Numeric input                 |

## Pre-built profile sections

In addition to schema-driven forms, the right panel surfaces curated sections for common profile areas.

### Personal contact details

First name, last name, and email — mapping to the standard XDM person and personalEmail field groups.

### Consent and preference details

Boolean toggles for: Any Marketing, Email Marketing, SMS Marketing, Push Notifications, Phone Calls, Postal Mail, and WhatsApp Marketing. These map directly to the AEP consent and preferences schema.

:::BlockQuote
ℹ️ Fields marked as system fields or identity fields in the schema are rendered as **read-only** in the form. They are displayed for reference only and are not included in the outgoing update payload.
:::