AEM as cloud and Generic List (ACS Commons) DAM metadata Schema - Options not saving in the dropdown

[sanketd27011989]

Metadata schema where we are using the Generic list to load the drop downs . A generic list with all options was created. Pasting the generic list path in the schema settings under “Add Manually” populates all options correctly.
Problem: After saving the metadata schema , options do not persist vanish.
Observation: Issue occurs only when the dropdown contains more than ~1,000 options. Smaller lists work as expected.
Visibility and choices rules can only be configured after the dropdown options are populated and saved.

Please assist me how I can save more than1000 value in list

[AnjaneaiSri]

Hi @sanketd27011989 

I recall seeing a similar problem in the past with AEM 6.5.18. Can you open the XML for metadata schema manually and see if the 1000+ nodes appear cq:dialog as child nodes. I believe the problem appears as node structure is too large and it fails/trucates (it used to truncate later options in my case).

Workaround - Try to point to external datasource like a JSON to call your dropdown options, that should solve your issue.

[giuseppebag]

hi @sanketd27011989,

It's possible that you cannot see the saved value because it isn't displayed in the rendered dropdown. However, the value may have been previously saved— you can verify this using CRXDE.

To address the issue, here are my recommendations:

• Avoid having large single dropdowns with over 1,000 options. Instead, consider using multiple dropdowns if any grouping logic can be applied.
• Implement cascading dropdowns.

Let me know if you need further assistance!