AEM Personalization with contexthub - component breaking

[iamaemuser]

Hi All,

There are certain components in our AEM application which read certain values from its parent pages. When we target such components, component is breaking, because now path for the component is different, now its from /content/campaign, when it try to read from parent path, component is breaking. Is there any way to fix this? Please advice.

@arunpatidar @SureshDhulipudi 

[EstebanBustamante]

Hi,

Ideally, your component should work in isolation from other components. Is there a way to refactor those components to read properties from an external common location (e.g., an AC Commons list)? You could also explore leveraging XF, which maintains a single source of truth and can be reused in several places. If none of this works, you might consider working around where these properties are being read and directly setting the path from which they will be pulled, instead of trying to infer the correct path.

Please check this thread for more ideas: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-pull-data-from-auth... 

Hope this helps!

[iamaemuser]

Hi @EstebanBustamante 

Thanks for your reply. Our site has MSM and under root folder of each sites, there are certain properties which will be used in multiple components. Currently the problem that we have is, when these components are personalized, its breaking. There are many such components. Is there any way we can make a common fix for all components.

[kautuk_sahni]

@iamaemuser Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!