hi @Himanshu_Jain, There is an out-of-the-box feature that allows you first to export all metadata into a CSV file. After your offline editing, you can import it back into AEM. More info here.

IMHO, the best solution is to address the root cause by avoiding the embedding of the jar, if possible. As a last resort, you could instruct SonarQube to exclude embedded jars or generated classes from the analysis to suppress false positives. 

hi @Arthiselva, Your SlingDataFetcher implementation and registration are the right starting point, but you also need to declare or extend the GraphQL schema to include a new field (nodeName) in the relevant GraphQL type exposed by Content Fragments.Please take a look here and here.   

hi @BhanuMa,I've a few questions:Are you possibly using classes intended for JUnit testing within your regular code? If so, you should replace them with classes from a different package or jar.<scope>test</scope>to the dependency and remove the embed, though.From your Sonar message, the embedded jar...

hi @SDusane,can you check if the folderMetadataSchema property of the folder node under ./jcr:content has the path to the schema form?

Have you tried removing the partdefault "/content/dam"from the code?Have you checked if this issue occurs in other OSGI services? The configuration file appears to be fine (source), but please review it to see if you overlooked something.   

hi @vashishth47,commands like export NODE_TLS_REJECT_UNAUTHORIZED=0 and npm config set strict-ssl false only influence client-side certificate validation and do not affect issues where the negotiated TLS version is unsupported or when the server expects a higher protocol version than your client is ...

Your model says it adapts from Resource.class, but HTL uses the SlingHttpServletRequest as the adaptable by default when using data-sly-use. Because the model isn’t configured to adapt from request, adaptation fails and returns null. Change your model to adapt from SlingHttpServletRequest.class@Mode...

You could split the Operation into Batches: Instead of processing all 10,000 pages at once, break the operation into smaller batches (e.g., 100 or 500 pages per batch): it reduces the number of simultaneous cache flush requests and minimizes the risk of overwhelming the dispatcher or author instance...

hi @Saiteja120, Please check if this meets your needs: https://github.com/adobe/aem-uix-examples/tree/main/cf-editor-form-field-dropdown-sample