Duplicate File Names in Vault

[Anonymous]

I tried a Vault copy design of an assembly and parts copying the assy. with a new name and copying parts with the same name. I placed all these in their own separate folder thinking the folder would protect the duplicate part file names. I received an error stating file names needed to be unique throughout vault.

Is this standard with Vault or is it unique to my particular Vault settings? I am not Vault admin. but have been given limited access.

[mdavis22569]

Yes someone who has ADMIN rights needs to go in and turn them off or you need to rename your files

What type of Vault (Basic-Work-Prof) 

and what year?

[Anonymous]

You're saying this is in the Vault settings? And, what would need to be turned off?

[Anonymous]

Vault Professional 2014

[Curtis_Waguespack · Accepted solution]

Hi Gerard.Storella,

See link:

http://help.autodesk.com/view/VAULT/2014/ENU/?guid=GUID-966D7736-07DB-4F69-88B8-ED18996FA0AD

Note too that there is a separate Vault forum:

https://forums.autodesk.com/t5/vault/ct-p/2004

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[Mark.Lancaster]

@Anonymous

Although @Curtis_Waguespack has given you information/solution..  I wanted to add to this..

My first thing..   Be very careful is disabling Enforce Unique File Names.   Without it you could set yourself, your organization, your Vault up for issues.  Each file should have its own unique file name.

Second thing..  Why would you copy anything and leave it the same name?  Why are you copying the same file into different folders?  You will be causing a nightmare if you continue to do this?  These are bad Vault practices and should be avoided at all cost.

[mdavis22569]

That's what I was trying to say ..but got tied up with another question 

I'd re-name it ...helps eliminate a lot of future issues

Adopt the good practices now ..but a problem later (Just my opinion)

Mike

[Curtis_Waguespack]

Hi all,

I was always told that if you didn't use unique file names in Vault then three of the four horsemen of the apocalypse would show up and sprinkle crab grass seed in your lawn, or some other horrible thing. But if you use Frame Generator you're going to either have non-unique file names or spend a lot of time renaming frame files.

I currently work with a Vault that has 35 - 50 users and the unique files names option is turned off. We do have some crabgrass in the lawn out front, but other than that all is well.

I typically recommend turning off the unique file name option in the project file settings too, as it doesn't actually prevent the use of non-unique file names, or do anything particularly useful, but slow down file resolution searches.

With all of that in mind, I see no reason to be copying files and leaving the file names the same, unless they are Frame Generator files, etc. If they are just regular design files, then your numbering scheme and overall process should steer you toward unique file names. That is far more important than the Vault setting in my opinion.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[Curtis_Waguespack]

I wanted to clarify my last reply, in case someone reads this thread and interprets what I said as "Unique File Names are not needed"

That is not at all what I was intending to say.

Unique file names are very important. But if I feel like a strong well thought out design process and naming scheme, should not result in file names that are not unique, and therefore the "nanny" settings to enforce these things are not required, if we know the importance of not having design files named the same name.

If I looked at your files, I wouldn't expect to see 2 Excel files named the same thing, let alone 2 Inventor files, when we have a strong process and naming scheme in place to tell us what the files should be called even before they are created.

However, if there is no such process or naming scheme in place then forty-seven bracket1.ipt files in a Vault can and likely will happen if this setting is turned off. And if there are that many bracket1.ipt files, there are almost certainly going to be bunch of Drawing1.idw files, and so on. And that's the reason we're all told to leave this Vault setting on.

My point is that assuming we are using are following a good naming scheme that precludes like file names, then turning the Enforce setting off in Vault is not a big deal

Hope that clarifies things.

[mdavis22569]

Oh I didn't think that ......