We are using a custom xtype to create cusom multifield lists. The xtype takes the declarations from our dialog, and creates repeatable sections based on your standard dialog xml.
We have created another custom xtype, which is a select box, that populates the options based on a function which returns some values in a JSON object from a content node. It works nicely using optionsProvider.
What happens though is when we declare our select xtype within our multifield xtype, the optionsProvider does not fire, hence not populating the options.
Does anyone know if there is a known issue whereby optionsProvider isn't called in such circumstances (nested xtypes)?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi There,
Thanks for reaching out to Adobe Community.
See if the below articles help:
http://helpx.adobe.com/experience-manager/using/creating-custom-xtype.html
http://helpx.adobe.com/experience-manager/using/dynamically-updating-aem-custom-xtype.html
http://helpx.adobe.com/experience-manager/using/creating-touchui-xtypes.html
Thanks!
Views
Replies
Total Likes
If possible - its recommended to avoid using nested xtypes.
Views
Replies
Total Likes
Hi There,
Thanks for reaching out to Adobe Community.
See if the below articles help:
http://helpx.adobe.com/experience-manager/using/creating-custom-xtype.html
http://helpx.adobe.com/experience-manager/using/dynamically-updating-aem-custom-xtype.html
http://helpx.adobe.com/experience-manager/using/creating-touchui-xtypes.html
Thanks!
Views
Replies
Total Likes
Thanks for both of your replies. I have seen the articles you provided links to Shekhar. I might have to rethink my approach - I do think the nested xtypes is getting a bit messy.
Views
Replies
Total Likes
Views
Likes
Replies