ÃÛ¶¹ÊÓƵ

Documentation

Content fragment model fails to load with many properties in AEMaaCS

Last update: Thu Jul 03 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When editing a Content Fragment model in ÃÛ¶¹ÊÓƵ Experience Manager (AEM) as a Cloud Service – Assets, the editor fails to display all fields if the model contains a large number of properties. To resolve the issue, reduce the number of fields in the model to improve visibility.

Description description

Environment

  • Product: ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) – Assets
  • Instance: Development

Issue/Symptoms

  • After adding multiple properties like tab placeholders and text components, the editor fails to display all components when reopening the model.
  • Components are correctly saved and visible in authoring mode and you can also inspect them via CRX/DE, but they don’t appear in the editing interface.

Cause

This issue occurs due to a known limitation in the Content Fragment Model Editor’s UI rendering capabilities. Models with 30–40 or more fields often fail to render completely.

Resolution resolution

To fix the issue:

  1. Open the Content Fragment model and count the total fields.
  2. If the model has 30 or more fields, split it into smaller fragments.
  3. Organize fields logically to reduce complexity and improve visibility.
  4. Reopen the model to confirm all components are now visible.

For further assistance, contact ÃÛ¶¹ÊÓƵ Support.

Managing Content Fragments in the AEMaaCS user guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f