TouchUI Multifield Not Saving in Editor Mode — Three Things to Check

If your AEM multifield saves correctly in Preview or Publish but loses data in Edit mode, it's almost never a caching issue. Here are the three root causes to check in order.

1. Missing composite Property

This is the most common cause. Your multifield node needs `composite="{Boolean}true"` otherwise AEM writes flat properties instead of child nodes, which behaves inconsistently between edit and publish rendering.

<items
    sling:resourceType="granite/ui/components/coral/foundation/form/multifield"
    composite="{Boolean}true">

2. Sling Model Reading Wrong Structure

With `composite=true`, AEM stores items as child nodes not a String array. Your Sling Model needs `@ChildResource` not `@ValueMapValue`:

// Use this for composite multifield
@ChildResource
private List<Resource> items;

3. WCM Mode Hiding Output in Edit Mode

Check your HTL for `wcmmode.disabled` conditions that might be hiding rendered output specifically in edit mode.

Fastest Debug Step

Open CRXDE after saving the dialog. If composite multifield is working correctly you'll see numbered child nodes (`item0`, `item1`). If you see flat properties, the composite property is missing or wrong.

That one CRXDE check tells you immediately which of the three issues you're dealing with.