Vault Collaboration 2010 - Non unique Visualization file

[john.dow]

Upon pressing the Update... view (DWF file), we receive the msg below, what might this message mean?

Update View Restrictions
Visualization file cannot be created due to vaulting restrictions
Restriction: Non unique visualization file

What is a non unique vis file?

[polo.zhenshi]

Hi John,
Could you check whether you have turned the 'Enforce Unique File Names' option on(Tools->Administration, Files tab). If so, could you turn it off, then try to update view again. I think there may be such dwf files(same name) already exist in your vault.
Regards,
Polo

[djohnson1976]

I experience this when I rename a file (i.e. File "A" to File "B") for the purpose of checking in another file with the first name (i.e. File "A"). The problem is that there is a DWF file for File "A" already in the Vault (even if its link was broken during the rename process, it is still an orphan DWF sitting in the Vault). When you load the new File "A" it wants to create the DWF "A.dwf" but it is already there. Could this be what is happening?

If you are not an administrator, you may not have the ability to turn off the unique part number setting even for a quick thing like this. The other option is to go to Tools > Options and check the "Show hidden files" button. When you look in the folder, you can see the DWF file (i.e. "A.dwf") and (hopefully if you have the permission) delete it. Kind of a pain. I would hope that future releases of Vault would have a check box in the rename dialog wizard to also rename the associated DWF files so this does not occur.

Hope this helps.

Dan

[polo.zhenshi]

Thanks for your posting, I have send your wishlist to the product designer.
Thanks,
Polo

[LOONYLEN]

Has this issue been reviewed, as I am having this very same issue mentioned above two years later (using 2012).

Is there a better way to deal with this issue that I'm not aware of? The two "Workarounds" mentioned above are not acceptable, as the number of times this would need to be done in one day would be overwhelming. It seems to me, if you're deleting a file from the Vault the .dwf should automatically be deleted as well. The .dwf files are typically hidden, so what would I need to keep a hidden .dwf file in the system for? Turning off the unique file names is unacceptable because we would like to keep our Vault free of duplicates. How should I proceed?

Thanks,

Len