Skip to main content
dmescia2
dmescia2
Level 4
May 7, 2026
Solved

Handling References when you Have Duplicates

  • May 7, 2026
  • 2 replies
  • 56 views

When designers are using Asset Link to link to image files in the DAM via InDesign, the DAM is relating it to a duplicate image from a different path when the InDesign file is uploaded to the DAM. We have a current workflow that requires us to create duplicates. I am working on changing that workflow to eliminate the need for the duplicates but we aren't ready yet to do that. So my question is:

 

When files with linked assets are uploaded to the DAM does AEM look for the first asset with that hash to relate it to or does it look for the one originally specified by Asset Link?

Best answer by SubbaraoGa1

​@dmescia2 

AEM is not resolving those uploaded InDesign references by file hash.
For uploaded .indd files, AEM fetches references by querying repository assets using XMP metadata identifiers — specifically xmpMM:InstanceID and xmpMM:DocumentID. That means the matching behavior is tied to those IDs, not to SHA/hash-based duplicate detection, and not reliably to the original DAM path that Asset Link showed at placement time.

Sources:

2 replies

avesh_narang
avesh_narang
Level 4
May 8, 2026

As per my understanding Hash is only for duplicate detection, not linking. Linking will still be based on specified Asset Link.

Thanks !

    S
    Adobe Employee
    SubbaraoGa1Adobe EmployeeAccepted solution
    Adobe Employee
    May 8, 2026

    ​@dmescia2 

    AEM is not resolving those uploaded InDesign references by file hash.
    For uploaded .indd files, AEM fetches references by querying repository assets using XMP metadata identifiers — specifically xmpMM:InstanceID and xmpMM:DocumentID. That means the matching behavior is tied to those IDs, not to SHA/hash-based duplicate detection, and not reliably to the original DAM path that Asset Link showed at placement time.

    Sources:

    dmescia2
    dmescia2Author
    Level 4
    May 8, 2026

    That’s unfortunate. This opens the door to risk. AEM does not manage duplicates well or granular permissioning and governance so its pretty easy for duplicates to work their way into the system. This manner of finding references makes it imperative that you eliminate duplicates or you risk the files referencing a dupe instead of the original. That in turn makes things like rights management extremely challenging.

    S
    Adobe Employee
    SubbaraoGa1Adobe Employee
    Adobe Employee
    May 14, 2026

    ​@dmescia2 Yes — that is the right conclusion.

    Because InDesign reference resolution is based on DocumentID / InstanceID lineage rather than a governed "approved original asset" concept, duplicates turn from a cleanup nuisance into a content-governance risk. In practice that means:

    • single source of truth is weakened
    • rights / expiry enforcement becomes unreliable
    • users can unknowingly place or relink to the wrong asset
    • legal takedown or replacement actions become harder, because "the asset in use" may not be the canonical one you thought it was

    Adobe's own duplicate-governance material frames duplicates as a governance and compliance problem, specifically calling out version-control issues, policy/metadata gaps, legal-removal complexity, and erosion of trust in the DAM.

    https://experienceleague.adobe.com/en/perspectives/best-practices-and-tips-for-getting-started-with-aem-assets


     

    Terms & ConditionsAccessibility statement

    Loading footer...