DocumentationExperience Cloud KCS

Folder names display as numeric IDs after migration in Adobe Experience Manager

Last update: September 3, 2026

This article explains why folder names in Adobe Experience Manager (AEM) may appear as numeric IDs or system-generated names after a migration and provides steps to restore human-readable titles.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

  • After migrating to a newer version of AEM, folder names in the repository display as numeric IDs or system-generated values instead of human-readable titles.
  • The jcr:title property is missing from the jcr:content child node of affected folders.
  • Identifying folder contents becomes less efficient, requiring additional folder lookups.

Cause

This behavior is often observed after migration events or when custom folder creation processes do not set the jcr:title property correctly.

Resolution resolution

To resolve the issue, verify and update the jcr:title property for affected folders.

  1. Identify affected folders.

    • Browse the repository and note folders displaying numeric IDs or system-generated names instead of human-readable titles.

  2. Check the jcr:title property.

    • For each affected folder, verify whether the jcr:title property exists on the jcr:content child node.
    • In AEM, use CRXDE Lite or another repository browser:
    • Navigate to the folder (for example, /content/dam/your-folder).
    • Expand the folder and select its jcr:content child node.
    • Verify that the jcr:title property is present and correctly set.

  3. Add or update the jcr:title property.

    • If the jcr:title property is missing or incorrect, add or update it on the jcr:content node.
    • In CRXDE Lite, right-click the jcr:content node and select Create Property.
    • Enter jcr:title as the property name and set the value to the desired folder title.
    • Save the changes.
    • Repeat for each affected folder.

  4. Verify the results.

    • After updating the jcr:title properties, refresh the repository UI and confirm that folder names display as human-readable titles.

  5. Review folder creation processes.

    • Ensure that any custom or automated processes responsible for folder creation are configured to set the jcr:title property on the jcr:content node for new folders. This helps prevent the issue from recurring.
recommendation-more-help
experience-cloud-kcs-help-kbarticles