DocumentationExperience Cloud KCS

Custom asset picker not supported in composite multi-fields in AEM Universal Editor

Last update: July 31, 2026

This article explains the current limitation where a custom asset picker field doesn’t function correctly when used inside a composite multi-field container in Adobe Experience Manager (AEM) Universal Editor. Use supported field types or alternative component designs to avoid this behavior.

Description description

Environment

Adobe Experience Manager (AEM) Universal Editor / Document Authoring (all versions)

Issue/Symptoms

  • A custom asset picker component (e.g., custom-asset-namespace:custom-asset) does not function as expected when placed inside a composite multi-field container (a container component with multi: true).

  • The custom asset picker works correctly as a standalone field, but fails to render or operate properly when nested within a composite multi-field.

  • No explicit error messages may appear, but asset selection and value binding do not work as intended in the nested context.

    Example component model definition:

    code language-none 
    {
  "component": "container",
  "name": "saleImages",
  "label": "Sale images",
  "multi": true,
  "fields": [
    {
      "component": "text",
      "name": "saleName",
      "label": "Sale name",
      "valueType": "string"
    },
    {
      "component": "custom-asset-namespace:custom-asset",
      "name": "SaleImage",
      "label": "Sale image",
      "description": "This image will be used for any sale that doesn't have a specific image defined.",
      "configUrl": "/content/dam/image.config.json",
      "required": true
    }
  ]
}

Resolution resolution

  1. Confirm that only simple field types (such as text, reference, aem-content) are officially supported for use with multi: true in Universal Editor. See Universal Editor field types. Note:

    • Container components with valueType: array (composite multi-fields) are not currently supported in the Universal Editor properties rail for all field types.
    • The component model documentation describes composite multi-fields as an advanced pattern and does not guarantee compatibility with all custom or extension field types.
    • Monitor Universal Editor release notes and documentation for future support of advanced composite field patterns.

  2. Use the configurable asset picker extension as a single field (one asset value per field). Note:

    • The extension is designed and tested for use as a single field, not for nested or repeated use within composite multi-fields.
    • Support for nested data structures such as saleImages/item0/SaleImage is not currently implemented or documented.

  3. Avoid placing custom asset picker fields inside composite multi-field containers in Universal Editor until official support is documented.

  4. If this functionality is critical, submit a feature request through the AEM product feedback channels.

  5. Composite multi-fields and custom asset picker extensions are not currently supported together in Universal Editor due to limitations in nested field handling and extension compatibility.

recommendation-more-help
experience-cloud-kcs-help-kbarticles