4. Dynamic Edit Forms
4 min
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
- 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.
- 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.
- Input type inferenceThe form renders the correct control based on the XDM field type.
- 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.
âšī¸ 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.