Documents with the same ID

This can occur if some documents have been replicated to the vault, for example during the cloud migration.

The metadata card displays the ID of the document in the vault where it was originally created (referred to as the original ID). The document still has a unique ID in the current vault (called the internal ID), but this is not shown.

This is normal behavior and shouldn't cause any technical issues. However, there is a potential risk of user confusion if someone happens to refer to documents by their IDs.

The user guide provides more information about the different IDs: Why are there objects with the same ID in the vault?

At the end of that page, there is also a tip explaining how to check the document's internal ID by adding an automated property to the metadata card.

This can occur if some documents have been replicated to the vault, for example during the cloud migration.

The metadata card displays the ID of the document in the vault where it was originally created (referred to as the original ID). The document still has a unique ID in the current vault (called the internal ID), but this is not shown.

This is normal behavior and shouldn't cause any technical issues. However, there is a potential risk of user confusion if someone happens to refer to documents by their IDs.

The user guide provides more information about the different IDs: Why are there objects with the same ID in the vault?

At the end of that page, there is also a tip explaining how to check the document's internal ID by adding an automated property to the metadata card.

Hi Joonas,

Thank you so mush for explanation.