AEM Asset Metadata Export - ability to save/reuse properties to be exported | Community
Skip to main content
November 15, 2022
Investigating

AEM Asset Metadata Export - ability to save/reuse properties to be exported

  • November 15, 2022
  • 2 replies
  • 665 views
Request for Feature Enhancement (RFE) Summary: Ability to save/reuse properties to be exported in Metadata Export
Use-case:

Issue 1

There is no reporting function in the DAM. I mean there is a reporting capability, but it suffers from the same issue that the metadata export suffers from; namely, you have to enter the metadata fields you want to report on, one by one. Laboriously. And once you have done this once, there is no ability to save the report/metadata export so the next time you want to do either you have to go in and re-create the whole extract/report again.

 

When you add properties to be exported, it is not a multi select screen so the task is painful when you need to export a big list.

 

Issue 2

You can get around Issue 1 by selecting the All option to get all metadata fields…

(See screenshot Issue 2)

But for some reason despite us only having about 90 metadata fields, the ALL options produces a CSV of anywhere from 200-3000 metadata fields, depending on how many assetpaths it returns. This renders the Export ALL option completely useless because the CSV file generated for any large number of assets is so big that Excel cannot open it.

Current/Experienced Behavior: See use Case
Improved/Expected Behavior: Ability to multi select properties in one go (not multifield - Add Property) and ability to reuse this selection when I needed re-create this export again in the future.
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaaCS
Customer-name/Organization name: Coles
Screenshot (if applicable):

Issue 1

 Press Add

 

 

Issue 2

 

Code package (if applicable):  

2 replies

kautuk_sahni
Community Manager
Community Manager
November 16, 2022

@ec2ec2_2 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference ASSETS-18076. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Kautuk Sahni
New Member
September 9, 2025

Hello @kautuk_sahni @

We would like to know if the above idea has been implemented, or if any workaround has been shared. 
In our use of the AEM Asset, we are facing this same difficulty and would like to know if we could reuse a specific set of metadata fields, or we could add a third option to the Dropdown menu, after All and Selective ?