Hi @ssin93 ,There are two ways through which you can achieve this:1. Use AEM’s GraphQL APIs for Content Fragments which supports headless CMS scenarios wherein external client applications render experiences using content managed in AEM.Checkout this article for more details on it:https://experience...

Hi @sreenu539 ,There are some dependency in pom which are not compatible with uber 6.5.17. Please make sure there are no conflict among them. Make sure to updtae the dependency one by one.ThanksTarun

Hi @gururajkoni69 ,You can use AEM remote SPA with next JS and can use AEM editor functionalities as-is for content management. Checkout below article for more info.https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/s... ThanksTarun

Hi @BrunoMM ,Can you try using plugin "jacoco-maven-plugin" in the pom file and check for the sonar coverage.Thankstarun 

Hi @Jniza ,Could you see if you are getting any error in browser console?Also when you click on create folder try to see in browser network tab for folder schema call.ThanksTarun

HI @ashish_mishra1 ,One way to handle or replicate this is that you write an ajax call on image selection. After that hit a servlet which will load a service which in turn will look or fetch all the required property by reading the node.ThanksTarun

HI @Santhosh_Talepalle ,Can you check in chrome dev console if you see any error.ThanksTarun

Hi @Vani1012 , Please change enable property to false for below path in CRX:/etc/workflow/launcher/config/update_asset_create and /etc/workflow/launcher/config/update_asset_mod launchers configuration.Hope this helps!ThanksTarun

Hi @jayv25585659 ,Can you try CRX2OAK migration tool as it may help in migrating version across.You can follow below link for more details:https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/using-crx2oak.html?lang=en ThanksTarun

Hi @robertol6836527 ,Are you getting the result in form of JSON, you cache the json file in AEM dispatcher or you can cache the entire page where the component is being used.