We have TONS of useless files (parts / assemblies) that we need to delete from commonspace. It is a huge hassle trying to figure out a safe way to do this. Our administrator is confused with the ambiguous language that comes from the WindChill platform. For some reason WindChill tries to associate parts & assemblies that have NOTHING to do with the file we're trying to delete. This is especially apparent with parts / assemblies that once had family tables associated with them. We find it necessary to occasionally break up the family tables. Then we try to delete the various stand-alone files as they are no longer useful, but we have constant failures within WindChill.
A good example...........creation of XYZ.asm with 3 instances:
XYZ_1.asm
XYZ_2.asm
XYZ_3.asm
We discover that instances 2 & 3 are not needed, so we remove those instances from the table (as well as from any drawings). We check in the assembly, go to commonspace to remove the two instances and we have trouble. We see verbage like "cannot delete file without first deleting XYZ.asm -2". We assume -2 refers to the iteration number, whereby we're required to delete the iteration where the two instances were once located. What we don't know is how to find iteration -2 to delete it. The only options we see are "delete all iterations, delete latest iteration, delete all revisions". It's very confusing.
Anybody know how to help?
