Hi SeanDid you ever manage to get it done? If yes, please share how. Sneh

Description - There should be a way of introducing parent child relationship in AEM component dialogs (like we can in multifield). If there are two instances of one component included in another, the ansence of such a functionality leads to a lot of duplicate code.   Usecase example is for an AEM + ...

@adobechat Yes, my bad. I'm new to the forum. I'll submit it there and delete this if it lets me. -Sneh

Hi @Anmol_Bhardwaj I know your last comment wasn't a correct reply but I think there isn't one that exists right now. It was, however, a good suggestion to submit an idea, which I did :). So, I marked it as the correct answer.

Description -There should be a way of introducing parent child relationship in AEM component dialogs (like we can in multifield). If there are two instances of one component included in another, the ansence of such a functionality leads to a lot of duplicate code. Usecase example is for an AEM + Ang...

@Anmol_Bhardwaj I thought as much. I'm not an Angular Developer and it just seemed so easy to do in HTL. However, I thought we can't be the only ones to include one component multiple times with different node names to store in under while using a JS framework.I wish a node name was allowed under fi...

Hi @Anmol_Bhardwaj Thank you for replying to my query. There is no HTL code, only Angular. So, we're restricted to implementing a solution in dialog. Something like a fieldset with a node name (primaryCTA / secondaryCTA etc) and including the link component tab there, instead of having same fields d...

We have an AEM + Angular code setup. There is a requirement to add a reusable link object/resource, that can be added to many different dialogs under different resource names "primaryCTA", "secondaryCTA", "link" nodes in Banner component, for example.It is as easy as doing a <sly data-sly-resource="...