Awesome idea @krati_garg ! 1. I can get the upload report which has the jcr:created property, sort it with path column. 2. Then sort the export sheet with path. Both sheets will now be in same sequence. 3. From here I can copy thejcr:created column from the report sheet to the export sheet and use i...

We’re doing metadata update for numerous assets using the bulk metadata export feature in AEM Assets.   Apparently, the export doesn’t have any property for when the asset was uploaded/created in AEM. I would expect: jcr:createdor dam:created properties, but they aren’t there in the exported CSV. I’...

Is this the DAM Event Handler that you're using? What properties have you selected to record?   These events gets recorded and saved in CRXDE under the respective user's account (/home/users/...):

No worries @AEM_PARTY , thanks for further explanation. I think I understand your use case now, but I also think we're not using the correct terminology ('saved') which is causing the confusion.   When a blank CF is created, it is in a 'saved' state. Maybe what you're after are the CFs which are not...

I tried to reproduce the use case, but I'm able to get the create date of the content fragment. Below are my steps, let me know if any pf the steps are incorrect as per your use case:   1. Created a new blank content fragment called 'myCF1'.   2. No content is yet saved in the content fragment, and...

Hey @huadongzhou , would you like to connect on a call maybe? I think talking through it would be much better to get in sync on this and faster as well  

Repository size increasing after deployment but not on all environments, makes me think of any digital content/assets being part of the deployment? Also agree with @Jagadeesh_Prakash , its worth running an offline compaction (and probably consistency check as well) considering the concern is around ...

Hi @SebasRios ,   I tried out the above use case, and I can see the payload in the CRX:   However, something to note here is that the workflow hasn't completed yet and is still running. If the workflow was to complete and archive, this payload also goes away.   Can you check if your workflow is st...

You are correct, the error indicates that AEM is unable to connect to the data source, that means we have to check the data source configuration.   Since you're using JDBC, you need to configure the Apache Sling Connection Pooled DataSource OSGi configuration: https://experienceleague.adobe.com/docs...

It certainly seems like a tricky one  Though there might be customisations that can be done to achieve this, I think thijgs will be much simpler if we tweak a bit the way the assets are organised in DAM.   Lets start by listing down the key requirements: Assets uploaded to DAM can have any of the t...