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,   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...

Are you using any particular service pack? Mine is a fresh AEM 6.5.17 without a custom code and seems ok. 

Could you try this in a fresh AEM instance? And just to be clear, the error isn’t related to an image referenced on a page; it stems from adding images or pages to the payload list (the screen in the background of the payload selector).

Hi, I’m using AEM 6.5.17, and the only way to encounter the error you’re seeing is if the asset or page is already in the payload list. This prevents you from adding the same asset or page twice. For example:   Added the asset: /content/dam/demo/icon.png   2. If I try to add the same asset again: /...

Hi,  Which version of AEM are you using? Are you sure this is not referenced on the page? How are you checking this? Can you provide more details about how you are selecting multiple assets and which UI you are using?