Last modified date not updated on asset metadata update | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by anupampat

Hi @prajwalre ,

 

That is because the DAM Metadata Writeback launcher might be disabled, check for the launcher its OOTB. Enable it and play around the conditions, I checked and it does work.

For more info about The Writeback workflow do check - https://suman-shekhar.medium.com/aem-custom-xmp-metadata-writeback-92f69a137489

 

2 replies

arunpatidar
Community Advisor
Community Advisor
March 13, 2024

Hi @prajwalre 
Confirmed: I have verified this in the local SDK, and I can affirm that there is no modification in the date when updating the metadata/properties of the assets.

 

Maybe you can raise a ticket to Adobe

Arun Patidar
anupampat
Community Advisor
anupampatCommunity AdvisorAccepted solution
Community Advisor
March 13, 2024

Hi @prajwalre ,

 

That is because the DAM Metadata Writeback launcher might be disabled, check for the launcher its OOTB. Enable it and play around the conditions, I checked and it does work.

For more info about The Writeback workflow do check - https://suman-shekhar.medium.com/aem-custom-xmp-metadata-writeback-92f69a137489

 

PrajwalReAuthor
Level 2
March 15, 2024

Thanks @anupampat for the response. Do we know why its disabled by default and given we've huge number of assets is it safe to enable?

anupampat
Community Advisor
Community Advisor
March 15, 2024

Hi @prajwalre , For the exact same reason you mentioned - a lot of assets, so if you enable it, the writeback is called on every asset metadata change & it creates a lot of load on the system. So if you can find the solution without using the launcher then please do so.

Refer https://suman-shekhar.medium.com/aem-custom-xmp-metadata-writeback-92f69a137489 , where the bolg says about Customizing XMP Writeback.