Hi,
I need to create a Nested Experience Fragment.
Requirement : We need to create an experience fragment in which a component is included and inside this component, we’ll having Multiple XF components ?
I tried to use OOTB and inside that Tried to include a component and inside component parsys, including new XF, --this sounds little confusing, I tried this way, (not a good way to proceed.)
But need help to get the requirement in more efficient way to achieve this.
Experience Fragment --- Component --- Experience Fragment
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
There is a known performance hit associated with nesting experience fragments (especially in conjunction with container components such as a responsive grid) due to how it calculates the allowed components and styles.
The recommendation instead is to leverage building blocks as a workaround:
I think, it is fine to use XF inside another XF.
There is a known performance hit associated with nesting experience fragments (especially in conjunction with container components such as a responsive grid) due to how it calculates the allowed components and styles.
The recommendation instead is to leverage building blocks as a workaround:
Thank you this article really helpful., But I am looking for the above question in AEM6.3.0, and this feature is from AEM6.4.
How can we achieve the above in AEM6.3.0
Views
Replies
Total Likes
Views
Replies
Total Likes
Hi @akhoury – this is correct, I remember in AEM 6.5 this became a huge issue for us and we had to build in guardrails to prevent too many nested levels, and circular references. This was in 2021.
Is Adobe's recommendation today the same? Nested EFs are to be avoided? Have there been improvements in this area in the latest AEM SDK in AEMaaCS? Thank you.
Views
Replies
Total Likes
@Tushaar_Infy I don't think the design has a problem. It should be okay. But I am also not sure about any known issues in doing so.