AEM Content Hub: Duplicate filter values after metadata field type conversion

Last update: August 24, 2026

In Adobe Experience Manager (AEM) Content Hub, duplicate filter values can appear after you convert a metadata field from a string type to a string array type using bulk metadata import. This behavior occurs when identical metadata values exist in different underlying data types.

Description description

Environment

Adobe Experience Manager (AEM) Assets
Content Hub (all versions)

Issue/Symptoms

After converting a metadata field, such as Product Category, from a string type to a string array type using AEM bulk metadata import, Content Hub displays duplicate values in the filter panel.
The Product Category filter displays two separate entries for the same value, such as Washer Dryer.
One entry originates from assets where the field is stored as a single string, for example "Washer Dryer".
Another entry originates from assets where the field is stored as a string array, for example [ "Washer Dryer"].
The duplicate values remain visible after the metadata type change and affect asset filtering in Content Hub.

Cause

Content Hub indexes metadata values based on their underlying data type. If identical labels exist as both a string and a string array, Content Hub treats them as separate filter values. Consolidation requires all assets to use a consistent metadata type and a subsequent reindexing.

Resolution resolution

Follow the steps below to resolve the issue:

Ensure that the affected metadata field is stored as a string array type across all assets.
Use AEM bulk metadata import to update any remaining assets that still store the field as a single string so that they use the string array type.
Reapprove or update the affected assets so Content Hub triggers a metadata reindex.
Open the relevant filter in Content Hub and verify that duplicate entries no longer appear and that each unique value displays only once.

recommendation-more-help

experience-cloud-kcs-help-kbarticles