Modified Date and Published Date fields are missing after an LTS upgrade in AEM Assets

After upgrading Adobe Experience Manager (AEM) to a new Long-Term Support (LTS) version, the Modified Date and Published Date fields do not appear in the Assets console for certain assets. This article provides steps to verify and resolve this issue.

Description description

Environment

  • Adobe Experience Manager Assets 6.5 LTS
  • Author environment following an LTS upgrade
  • Deployment type and exact LTS service pack/build to be confirmed

Issue/Symptoms

  • After you upgrade AEM, the Modified Date and Published Date fields are missing from the Assets console for some assets.
  • Metadata continues to display as expected on content pages.
  • The issue is reported primarily on Author and doesn’t affect every asset.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Check the asset’s metadata in the AEM Assets console:

    • Open the asset’s Properties dialog.
    • Check whether the asset contains the expected last-modified and last-replicated date values.
  2. Inspect the metadata request in your browser:

    • Open Developer Tools and select the Network tab.
    • Select the affected asset in the Assets console and inspect the request to .../jcr:content/metadata.json.
    • Check whether the request succeeds and includes the date values, or returns 403 or 404.
  3. Determine the scope of the issue:

    • Check whether the issue occurs only on Author or also on Publish.
    • Check whether all assets are affected or only specific assets.
    • Record the AEM 6.5 LTS service pack/build and whether newly uploaded assets are affected.
  4. Review customizations that could affect metadata retrieval or display:

    • Check custom configurations and overlays that affect the Assets console or asset metadata.
    • Review custom Oak index definitions if the metadata request or related query indicates an indexing issue.
  5. If the issue continues, check the current AEM 6.5 LTS release notes and Adobe Support updates for relevant fixes. When escalating, provide the exact LTS build, affected scope, sanitized network response, and relevant logs.

  6. After your checks or any applicable updates, reopen the affected assets in the Assets console and confirm whether the Modified Date and Published Date fields display as expected.

recommendation-more-help
experience-cloud-kcs-help-kbarticles