Options
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 15 subscribers
  • Views 1272 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Content replication Import lookup points to object in source vault

Admir.MFiles

Hi,

When importing content (using the content and replication import function), there is metadata (lookups) that points to objects in the source vault. The same content exists in the import vault, but with different IDs or GUIDs, even though the names are the same.

Is there any out-of-the-box solution available to adjust the import so that the metadata points to the objects in the import vault, rather than the objects in the source vault?

Thanks!

Parents
  • 0

    I found this in the documentation for replication and archiving.



    So it seems that it's only possible to refer it using the Object Guid and External ID?

    The problem during my imports is that looking on the metadata it seems correct but when opering the object by clicking on the blue link I noticed that it points to a copy of that object and not the actual object even though it exists in the import vault.
    The object icon has an arrow on it also.



  • 0 in reply to Admir.MFiles

    The icon with an arrow is a shortcut: Relationships Between Objects in Separate Vaults

    I don't think there's an easy solution to your challenge unless you can somehow make sure all the vaults are getting their data from the same source (an external system or a master vault from where the objects are replicated to other vaults).

Reply Children
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.