LiveCopy assets not publishing to Dynamic Media in AEM
After using LiveCopy to duplicate assets, publishing to Dynamic Media fails for some of them. Attempts to publish using various methods—including single publish, folder publish, quick publish, manage publication, and reprocessing—do not work. This occurs because LiveCopy copies asset metadata, including the assetHandle, which causes both the original and copied assets to reference the same Dynamic Media asset. To resolve the issue, exclude Scene7 metadata properties during LiveCopy operations.
Description description
Environment
- Adobe Experience Manager
- Dynamic Media Scene7
Issue/Symptoms
- Publishing to Dynamic Media fails for assets copied using the LiveCopy function.
- Attempts to publish using single publish, folder publish, quick publish, manage publication, or reprocessing do not succeed.
- The copied assets retain the same
assetHandlemetadata as the original assets, causing conflicts in Dynamic Media. - Both the original and LiveCopy assets point to the same asset in the Dynamic Media back office.
- When VirtualID is enabled, Dynamic Media requests fail if the asset at the expected path is unavailable or unpublished.
Resolution resolution
Follow these steps to prevent Scene7 metadata from being copied during LiveCopy operations:
-
For AEM 6.5, Open the OSGi Configuration Console at
/system/console/configMgr. -
Locate and edit the following configurations:
com.day.cq.wcm.msm.impl.actions.ContentUpdateActionFactory.cfg.jsoncom.day.cq.wcm.msm.impl.actions.ContentCopyActionFactory.cfg.json
-
In both configurations, exclude the property pattern
dam:scene7.*to prevent copying Scene7 metadata. -
For AEM as a Cloud Service (AEMaaCS), push this configuration change through the deployment pipeline.
This ensures that copied assets do not retain conflicting Scene7 metadata, allowing proper publishing to Dynamic Media.
Related reading
Live Copy Overview Console in the AEM as a Cloud Service User Guide