We are using dropdown as multifield in page properties. When the page properties are opened and dropdown values are selected and saved, they are stored in jcr as String array but when the page properties are opened, the selected values are not rendered and shows multifield dropdown as never edited.
Single dropdowns works fine.
Help Appreciated !!
Please have look at these two articles:
Both approaches store data in JCR differently.
Please find the part of the xml which renders multifield dropdown.
The same xml is used across component level and works fine. The configuration is stored node wise and renders correctly on opening the dialog but when used for page properties level, stores the configuration as string array and doesn't show anything on opening the dialog.
fieldDescription="Click '+' to add a new field"
fieldDescription="Select Resource Categories"
I see you're using this eaem-nested property, probably from this link? Experiencing Adobe Experience Manager - Day CQ: AEM 62 - Touch UI Nested ( Multi-Multi ) Composite M...
It is available as we are using the multifield dropdown or any combination of fields at component level and those work fine.
Are you trying to edit the properties in the editor or in the UI you get when you select the page in the sites.html/content/... and click on edit properties?
Yes I can understand that, but that was not what I asked. I asked if you're editing the properties via the editor.html or via the sites.html UI
Though I go from editor.html or sites.html, it opens : /mnt/overlay/wcm/core/content/sites/properties.html?item=pagePath.
Can you try switching to Coral UI 3 based resources. If you are using the same, remove eaem-nested property.
Properties at jcr:content doesn't get stored in form of items as it does at component level. it is storing as String array and could not read the values back from it.
Is this the case with Coral UI 3 multifield as well? Can you please post some screenshots of jcr:content node, highlighting the string array value.