Sorry to hear that. I think at this point, you should start a new AEM instance, install a fresh project (not the one you're currently using), and make sure a demo servlet works. Then, slowly add your servlet to this project and see if the issue appears. Lastly, install your code project to see if th...

Hi, Pls check if the bundle is active and the servlet is correctly exposed. 

Hi, If you are using Chrome, make sure you have set it up to display all the log statements in the browser console. If this is a testing environment you can always add the "debugger;" statement to stop the execution of the JS and see what's going on with the console statement. Hope this helps

Hi, Firstly, OSGi Events are deprecated, instead, you should use ResourceChangeListeners. Please read this blog about how this could increase your performance: https://cqdump.joerghoh.de/2022/02/03/the-deprecation-of-sling-resource-events/   Also, If you are using AEMaaCS, please explore if this wor...

Hi,  There are 3 things you could use here: 1. Once you select the original source of the launch, you can use the "Compare to Source" option, which will provide a visual representation of the changes made, but this is on a page-by-page basis. Still, this can be useful 2. When you use the "Promote L...

Hi,   Could you elaborate on how you are upgrading the SDK? Have you tried downloading the latest version to see if that resolves your issue? Please check this thread where the best approach to upgrade the local SDK is discussed: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-mana...

Hi,   I have noted this behavior before, and my opinion is that this functionality is intentionally broken because you are not supposed to overlay a node directly in AEMaaCS through CRX/DE. Since the AEM SDK is designed to mimic the cloud as closely as possible, there are certain aspects that may no...

Ah! You are right; the issue is that the "jcr:created" property is technically not part of the metadata but part of the assets themselves, which is why this tool is not exporting it. This will reduce your options. You could try relying on another metadata property instead of the "jcr:created" proper...

Hi,   I believe the options you outlined are the most viable for this scenario. I'm leaning towards the AEM Assets Post-Processing approach. Are you encountering any specific issues with any of these options?

Hi,   This seems really challenging to accomplish without coding options. Eventually, you’ll need to check each asset one by one without any custom code. Here’s how I think you could do it purely through the UI: Use the Metadata Export option (https://experienceleague.adobe.com/en/docs/experience-m...