AEM CSV metadata import or export fails due to formatting, delimiter, or header issues
In Adobe Experience Manager, CSV-based metadata import and export fails or behaves unexpectedly when the file uses an incorrect delimiter, includes hidden blank rows, or contains invalid schema headers. Controlled vocabulary fields fail to update when the imported value does not match the stored internal value, and multi-value fields import as a single string when headers are not defined correctly. Spreadsheet edits also introduce formatting changes that cause schema CSV imports to fail even when the file appears correct. To fix this, review the CSV structure, use pipe delimiters for multi-value fields, and verify headers and stored values before importing again.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- AEM Assets Essentials
- AEM Managed Services
Issue/Symptoms:
- Metadata import fails with CSV file has data in incorrect format.
- Multi-value fields import as a single concatenated string instead of separate values.
- Dropdown-option CSV import fails even when using the provided template.
- Metadata values do not update even though the import job completes.
- Multi-value date fields partially update or values disappear after import.
Root cause:
AEM expects strict CSV formatting for metadata import. Multi-value fields require the pipe character | as the delimiter, while exported values may appear with commas or semicolons for readability. Hidden blank rows, quotes, or other formatting changes introduced during editing can cause import failures. Incorrect column headers, including missing multi-value type notation, can cause AEM to treat multi-value data as a single string. Updates can also fail when dropdown or controlled vocabulary fields use display labels instead of the stored internal values.
Resolution resolution
To troubleshoot and successfully import metadata using a CSV file in AEM, follow these steps:
- Identify whether the issue occurs during asset metadata import or during metadata schema dropdown CSV import.
- Open the CSV in a plain-text editor and remove any completely empty trailing rows.
- Update all multi-value fields so values are separated with
|, for example:value1|value2|value3. - Correct the CSV headers so multi-value fields match the schema format used in an exported AEM CSV.
- For dropdown or controlled vocabulary fields, replace display labels with their exact stored internal values used by AEM.
- If a metadata schema dropdown import fails, download a fresh template from the Metadata Schema Editor and add rows in a plain-text editor, not a spreadsheet application.
- If multi-value date fields still lose values after import, test again with a clean local CSV. If the issue continues, contact Adobe Support.
- Convert any spreadsheet file to
.csvbefore importing. - If the issue persists, contact Adobe Support and provide the failing CSV file, your metadata schema definition, a screen recording of the error, and sample asset paths.