Fix incomplete AEM Assets bulk metadata updates with CSV import
Bulk metadata updates in Adobe Experience Manager (AEM) Assets may not apply to all selected assets when you update more than 100 assets at once. Use Metadata CSV import to update large sets.
Description description
Environment
Adobe Experience Manager Assets (all versions)
Symptoms
- When performing a bulk metadata update on more than 100 assets, the operation reports success for all selected assets, but only a subset actually receive the updated metadata value.
- The UI may indicate that all assets were processed, but after saving, only some assets reflect the new metadata.
Steps to reproduce
- Navigate to the relevant asset folder in AEM Assets.
- Filter and select all assets (more than 100, for example, 333).
- Perform a bulk metadata update for a custom field.
- Save the update.
- Verify individual assets after the update completes.
Cause
The Bulk Metadata Edit feature in AEM Assets View is limited to 100 assets per operation. Attempting to update more than 100 assets at once can result in incomplete updates, especially for custom metadata fields.
Resolution resolution
Follow these steps to resolve the issue.
-
For bulk metadata updates involving more than 100 assets, use the Metadata CSV import workflow instead of the Bulk Metadata Edit feature.
-
Prepare a CSV file with one row per asset, including the full asset path and the metadata value to be applied. Example CSV format:
assetPath,customField/content/dam/path/to/asset1.jpg,value/content/dam/path/to/asset2.jpg,value
-
Export a metadata template from AEM to ensure correct column headers and formatting.
-
Update the relevant metadata column in the CSV file.
-
In AEM, go to Create
>Metadata>Import, upload the CSV, and configure import options:- Batch Size: The maximum is 100 and the default is 50
- Field Separator: comma (
,) unless otherwise required - Asset Path Column Name:
assetPath - Launch Workflows: leave disabled unless needed
-
Start the import process.
-
After the import completes, check several assets from the beginning, middle, and end of the CSV to ensure the metadata was applied correctly.