2024 Jan 16 6:14 AM
2024 Jul 11 2:03 AM
Hi Srinivas,
I have a similar issue where the re-use component initializes with a stable id. Hence, we cannot have multiple usages of the same. Were you able to resolve this issue?
Thanks,
rahul
2025 Jan 10 5:30 AM
Hi Rahul,
@rahullohia
I don't have a solution yet, but I'm currently trying to get in touch with the Component Control team. I'll update the POST as soon as I have more information.
By any chance, have you come across any alternative approaches in the meantime?
Best regards,
Srinivas
2025 Jan 15 3:07 AM
Hi Srinivas,
Unfortunately, I had to change the design wherein I am using the same component instance twice using a switch.
Maybe you can try this approach instead of manually creating the views/controller where the component is initialized?
Thanks,
Rahul
2025 Jan 20 4:31 AM
Hello Rahul,
Thanks for sharing the info.
I tried adding the autoPrefixId="true" property and i was able to fetch these id's in the consuming application.
<core:ComponentContainer
id="comp1"
usage="someComponent"
manifest="true"
async="true"
autoPrefixId="true"
/>
Inside Component.js of consuming application,try checking the value in onBeforeRendering.
onBeforeRendering: function(){ console.log(this.getId()); }
2025 Jan 27 6:49 AM
This works just for standalone application. When integrated to FLP the getId() doesn't work