DocumentationExperience Cloud KCS

Metadata property is not copied during translation when an outdated source asset version is selected

Last update: July 30, 2026

When an asset is sent for translation in Adobe Experience Manager (AEM), a metadata property may not be copied to the temporary folder or translated asset if the translation uses an outdated asset version that does not contain the metadata. As a result, the translated content is missing the expected metadata values. To fix the issue, verify that translation is using the latest asset version that contains the required metadata and rerun the translation process.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

  • A metadata property such as legacyUniqueID at jcr:content/metadata/mc:legacyUniqueID is not copied to the translated output.
  • The property exists on the source asset and has the correct structure and type.
  • Adding the property to the translation configuration rules does not correct the issue.
  • The version selected for translation does not contain the required metadata property, even though the current version of the asset does.
  • The translated output is missing the expected metadata value.
  • Comparing the jcr:versionHistory of the asset shows that the version used for translation does not contain the updated metadata.
  • No explicit error message is displayed.

Root cause

The source version selected for translation did not contain the required metadata property. As a result, the translated output did not include the metadata value.

Resolution resolution

To address the issue, follow these steps:

  1. Open the source asset that you plan to send for translation and confirm that the required metadata property is present on the current version.

  2. Verify which asset version is used for translation.

    • Check the jcr:versionHistory property to identify the version used during translation.
    • Compare the metadata on that version with the metadata on the current version.
    • Confirm that the version selected for translation includes the required metadata property.

  3. If the version used for translation does not contain the required metadata, update the asset metadata and create a new version that includes the required property.

  4. Start the translation job again after confirming that the correct source version is selected.

    • If a version-selection dialog appears, choose the latest version that includes the required metadata property.

  5. After translation completes, review the translated output and confirm that the metadata property is present.

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