AEM Content Fragment model fields

Learn about the limitations and configurations for the number of fields in an Adobe Experience Manager (AEM) Content Fragment (CF) model.

Description description

Environment

AEM version 6.5.18

Issue/Symptoms

You might wonder if there is an official limitation on the number of fields you can add to a Content Fragment (CF) model. There is no explicit limitation on the number of fields a model can possess. This is because the content varies for each customer, and the numbers may differ accordingly.

The number of fields you can display with the default settings depends on the complexity of each field (how many view elements it requires to be displayed). Depending on the type of model fields used in the CF model, some will require more internal calls to be displayed. There is an option for the maximum number of internal calls that can be made and the number of fields that can be shown.

The setting (sling.max.calls) for these internal calls is kept at a low level because it is unusual to have a very large number of fields for one single Content Fragment model. However, if you have a valid use case, you can increase this value to accommodate the large number of fields. You can show more fields on the form by raising the value of thesling.max.calls OSGI configuration in ui.config/src/main/content/jcr_root/apps/customer/osgiconfig/config.author/org.apache.sling.engine.impl.SlingMainServlet.cfg.json.

Resolution resolution

We advise you to increase this amount gradually and only increase it until it can support the required number of fields rather than raising it to an excessively high number. This setting should be picked up each time the instance is restarted because it will be added to the configuration files.

Although it is possible to have a large number of fields in a single model, we recommend splitting the fields into multiple smaller models and fragments and using fragment references instead.