AEM Cloud Service — Composite Multifield in Content Fragments Editor(New Editor)

In our last post, we discussed the approach to customize the new Content Fragment Editor by adding a dynamic dropdown list. The method we previously used in the old editor — enabling a custom client library — does not work in the new CF Editor, as it is now based on the Universal Editor.

To enable customization in this new environment, you need to use the Extension Manager approach. For a step-by-step guide on how to implement dynamic dropdowns using this method, refer to the article: AEM Cloud: Enabling Dynamic Data Fields in the New Content Fragment Editor | by Albin Issac | Tech Learnings | Jan, 2025 | Medium

In this post, we’ll explore how to enable multifield support in the new CF Editor — a common requirement in many implementations. While one approach is to use a reference Content Fragment Model, having a true multifield is often more intuitive and flexible.

Most of the setup steps remain the same as with the dynamic dropdown example — we’ll just focus on the extension changes needed to support multifield input.

As a first step, add a JSON Object field to the required Content Fragment Model and assign it a unique name (e.g., compositeMultiField).
The JSON Object field type allows you to store multiple values in a structured JSON format within the JCR (CRXDE). At runtime, this field can be rendered as a multifield UI component, enabling authors to enter multiple sets of related data.