This content has been marked as final. Show 5 replies
Are you familiar with T-SQL? If so, you can run this query.
Select D.DocumentID, D.FileName AS [File Name], P.Path AS [Project Path]
From Documents AS D
INNER JOIN DocumentsInProjects AS DIP ON D.DocumentID = DIP.DocumentID
FULL OUTER JOIN Projects P ON DIP.ProjectID = P.ProjectID
WHERE D.Filename IN (Select Filename FROM Documents Where Deleted = 0
GROUP BY Filename
HAVING (COUNT (Filename) > 1))
ORDER BY D.Filename
I'm still puzzled why the default out of the box setting allows duplicate file names in the Enterprise Vault.
We have it on intentionally. Our work here is project based, not product based, so we pretty much duplicate file names for each job and they are kept separate by the different job folders.
Hello Jeff and Wayne-
Thanks for your responses, you have good points.
When I explain this setting to QA Admins at Medical Device Companies, they are shocked. For example in Agile, used by a lot of Medical Device Companies here in Southern California, duplicate file names are not allowed.
The concept of Duplicate File Names is counter-intuitive to them, it goes against their thinking.
I have grown to like it. A majority of file types I don't mind having duplicate file names; the CAD files are the exception -not the rule. It is easier to select the exceptions than vice versa.