AEMaaCS metadata schema dropdown strange behaviour with JSON path that has many values

Forum|Forum|2 years ago
March 8, 2023
2 commentaire
1004 vue

Hi,

We have a select dropdown field in our metadata schema which renders options dynamically with JSON path configuration. The list is configured in generic lists and configured the JSON path as per the ACS Commons documentation[https://adobe-consulting-services.github.io/acs-aem-commons/features/generic-lists/index.html].

This one specific field has about 350 items in list which in-turn will be rendered as dropdown options.

There are no issues when there is no value selected for the dropdown or if a value is selected at the beginning of the list and saved, the dropdown renders fine.

We're observing a strange issue when a value which is at the bottom or at the later point in the list is selected and saved. When the metadata editor is loaded again and we try to expand the select options it just flickers without opening the dropdown fully. The other dropdowns in the editor are working fine.

Please find below code snippet of the schema:

<_x0031_555091269245
    jcr:primaryType="nt:unstructured"
    sling:resourceType="dam/gui/components/admin/schemafield"
    emptyText="Select Option"
    fieldLabel="Series"
    jsonPath="/mnt/acs-commons/lists/daltile/series-list.json"
    name="./jcr:content/metadata/Series"
    ordered="true"
    resourceType="dam/gui/coral/components/admin/schemaforms/formbuilder/formfields/v2/metadataselect">
    <granite:data
        jcr:primaryType="nt:unstructured"
        metaType="dropdown"
        requiredCascading="default"/>
    <items jcr:primaryType="nt:unstructured"/>
</_x0031_555091269245>

Please find the recording here:

DAL_Metadata_Dropdown_Issue.mov

Thanks,

Sachin

Ce sujet a été fermé aux réponses.

Saravanan_Dharmaraj

Community Advisor

@hay12634-1 , it could be the number of items for the drop down. 350 items for a drop down is way too much i feel. When the editor loads and set the html for each option value and then set the selected value in the UI.

H

hay12634-1Auteur

@saravanan_dharmaraj This is actually an upgrade project from 6.3 and they have the same implementation working on 6.3. The only difference is the list is rendered from a custom servlet rather than a generic list.