@Sb2512  There is one similar thread comparing both. https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/sling-servlet-path-vs-resourcetype/m-p/322039   Hope it helps!

@montu639    I could see following on the release page of AEM modernisation tool Dialog Conversion Tool Since the intent of these tools is to transform content and not code, the Dialog Conversion tool has been removed as of version 2.0. The tool is still available in v1.0. However, since its additio...

@PoovithaSelvaraj  Try unpublishing the content and publishing it again. It will make the content unavailable for a while in publisher but it will update all nodes. Given that, unavailability for few minutes is not an issue!

Hi @varaprasadande1, placing packages in install folder works fine. You can use this approach.

You can populate this value in the HTML and later grab this value in JS while rendering the page.

@AEMLearner-1989 A similar use case has been discussed in the thread below.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/multi-tenant-deployments-using-cloud-manager/td-p/364123 The correct marked answer in the above thread might be interesting for you.I hope it helps!

Hi @Anudeep_Kumar  Could you please share the use-case?How are you planning to use the node name after defining it?

Yes, all renditions have been generated correctly.

@EstebanBustamante Yes, I have added this dependency but the behaviour of the smart crop assets are not same as image v2 component. both components shows a different smart crop image, image v2 works correctly but image v3 doesn't.

Hello, I am using image v3 component for one of the use case. Now, I have dynamic media enabled and when I drag an assets to this component. I can see the smart crop option enabled in the image component dialog. I have selected 'Auto' rendition in this dropdown but while rendering this asset in brow...