HI @Kalyan_ChakravarthyCh  , Could you please share more details , where are you stuck  ? And what are the errors/issues you are facing . Thanks 

HI @SushmaNa1 , try with this version  AEM SDK v2024.11.18751.20241128T090041Z-241100  or higher than this you will get these configurations. Thanks 

Please sahre more details like wise console log, error logs to find the root cause of the issue.

I comprehend your issue, and there are a few approaches you can take to address it:Initially, the dropdown should display only a default value upon loading, rather than showing all available options. The values will populate the dropdown only when the user or author clicks on that specific field, wh...

Based on the provided error screenshot, it appears that there is an issue with connecting to the necessary content fragment. Is your instance linked via the HTTPS port? Is your local universal editor service operational? Consider configuring the universal editor by referring to this document.- https...

Yeah Lokesh , I used this https://experience.adobe.com/#/aem/editor/canvas At present, the Universal Editor is compatible with AEM as a Cloud Service. There is a possibility that it will be available for AMS and on-premises versions of AEM in the future (I haven't verified the latest updates to see ...

Thanks for sharing, very well articulated with examples.

It would be great , if you can elaborate your use case . As getting runmode is altogether different from the registration of the servlet (path based or resourceType based ) . You can get the run modes in be and fe , and based on the condition you can apply the logic of the servlet .

I did local set up following the below url.https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/universal-editor/react-app-editing/local-development-setup Hope it helps you as well ! 

It appears that you are including unsuitable frontend libraries in the component.As you pointed out, certain components are utilizing the standard AEM React module, while others are employing a headless Next.js frontend.Please verify that the appropriate libraries are activated from the default comp...