1 person found this helpful
Which Cumulative Fix Pack are you using? I've heard CFP 11 can cause this behavior. There's a constant CQ.PAGE_PROPERTIES_MAX_RECURSION_LEVEL defined in /libs/cq/ui/widgets/source/constants.js that will interfere with paths like pagenode/jcr:content/level1node/actualpropertynode. You need to overlay that file and increase the recursion level to the depth you require.
Thanks for the quick reply. Wrongly mentioned version as AEM 6.1, but i am getting this error for both AEM6.1 and AEM 6.3.
Figured out something more:
When using custom multifield from within a component dialog (for example dialog of metatag component) the node structure which is getting created in crx is as below and everything is working fine
But while using the multifield from within Page Properties the node structure which is getting created in crx is as below:
Due to this improper creation of nodes , the page properties dialog is not able to fetch stored data. Any help on how can i resolve this?
Its Classic UI multifield, so I am assuming you would have written custom widget.
The format in which you want to store values can always be customized in setValue method.
Getting same issue multifield component with in page properties not working. Please suggest.
Have you created custom logic for this custom MF?
Please specify online Adobe Docs you are following for this use case so community can try and reproduce.