Universal Editor does not enforce “Maximum number of items” constraint from Content Fragment model

Hi ​@Mahesh_Gunaje 

You're right about the behavior you're seeing, and there's nothing wrong with your model.

1. Is this expected / known?

• The Content Fragment Editor correctly enforces Maximum number of items for multi‑value fields (as per the Content Fragment Model definition). https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/content-fragments/content-fragments-models
• Today, the Universal Editor does not consistently enforce the same max‑items limit for those multi‑value fields, which is why you can add a 4th item and it still saves. This is effectively a product gap/bug, not your misconfiguration.

2. Plans to align Universal Editor with CF model constraints

The documented direction for UE is that it validates Content Fragment fields based on their models (regex, uniqueness, etc.). https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/field-types

• However, enforcement of Maximum number of items for multi‑value fields in UE is not yet on par with the Content Fragment Editor. To track it formally and get updates, you should:
  • Raise an Adobe Support ticket and reference your observations (CF Editor vs UE behavior, plus screenshots).
  • Optionally log an Idea in the AEM Ideas portal so others can upvote it.

3. What to do right now

Until UE is updated to respect Maximum number of items for multi‑value CF fields:

1.Process workaround

• For fields where the max count is critical (like your multi‑value field with max = 3):
  • Ask authors to edit that field only in the Content Fragment Editor, not via Universal Editor.
  • This guarantees the limit is enforced before save.

This looks like a current limitation/bug in the Universal Editor. The Content Fragment Editor correctly enforces Maximum number of items, but UE can currently save more items than defined in the model. Until Adobe aligns UE validation with CF model constraints, the safe workaround is to treat the CF Editor as the "source of truth" for those constrained multi‑value fields (or add a custom validation step on publish), and log a Support ticket so the behavior can be tracked and fixed.