Update File Reference Command

[sara.lindfors-larsson]

Hi,

This new command "Update File Reference" is great to use after migrating files, but there is not much info regaring this command (except in the Read me file and Whats new).

When we used this command we selected the root of the vault ($) > Actions > Update File Reference, it started to update but without a warning/message it just stopped. So we had to do this folder by folder, which is not a great solution when there are BIG Vaults. And since we help different customers with this, big Vaults will come. 

So I'm wondering if anyone has any info to share when it comes to what to do and what not to do before using this command. Are there some log files that register why it just stopped updating the files? Are there things to think about before starting this command (To avoid issues (like this)) – like does every file have to be checked in/migrated? Etc. etc

Best regards

Sara

[lei.hong]

The Update File Reference command is designed to get the required information (from technical perspective) from the data migrated from previous release, so user can do rename/move on these lagecy data in Vault 2012. There is no warning or message (with all the files failed listed) only if there is any error during updateing. And any file in the folder selected or the subfolders will be updated so you don't have to do this folder by folder. If all the files are already updated, then nothing to do. Therefore, it will stop very soon. Let me know if this doesn't answer your question. 

[david_j2_myers]

I'm having the same issue as Sara.  We have a very large vault, on the order of 700,000+ files.  We use copy design  daily to create new assemblies from standards.  Since we were previously on 2011, everything in the vault is legacy (most earlier than that, back to 2005).  As Sara observed, doing an update on the whole vault just stopped without a message, obviously not completing.  Smaller folders were selected and updated, apparently successfully, although taking a very long time (hour or so depending).  I estimate it would take days to update the whole vault, if it would work at all.  It's not really practical to do this folder by folder.

Is there a way to do this offline?  Possibly as a server task, like a reindex or hot backup does?

[Richard.Rankin]

Hi Sara and David,

Autodesk has only recently been made aware of some issue with this and we are currently working on some solutions.

As soon as we have more information we will update you.

[DuncanAnderson]

.
3.5 years later, do we get an update ?

[marco_lorenz1]

I see the same behaviour persisting (observed with Vault 2015)

Any comments from Autodesk?

Is there an API method which may be used?

[Richard.Rankin]

There is no API or command line to run the Update File Reference tool.

If you need this function to be supported via the command line or API, it would most likely be treated as a wish\enhancement.

I would therefore recommend that you log the request in the Vault Ideas forum