Community Tip - Did you know you can set a signature that will be added to all your posts? Set it here! X
All,
I have seen posts where family table instances cannot be deleted from Windchill when I delete entire table of the generic. Those deleted instances are still tied to the generic and cannot be deleted. I think I read something about purging the itterations below the latest version. Not sure how to do that. Anyone know how to get rid of these dead instances? I am thinking, maybe if I had the instances in session, then deleted the table, the saved each instance, that may have been the way to go?
Wayne
If you have iteration 4 with 6 instances, and you check in iteration 5 with an empty table, you have to delete from top to bottom all, where used dependencies, from the first to iteration 4. Without deleting where used drawings and assemblies in Windchill, you can‘t purge the model and get rid of the unused old instances of the generic model.
Personally I‘m no longer a fan of keeping old iterations in the database. It’s a waste of time and cpu. Just work with the latest iterations is enough in 99.9% of all cases. Form, Fit and Function is important. Working with tons of unused iterations will slow down Windchil in the long run. Just think about the attribute search, you don‘t care about old values, but you waste cpu by excluding them on each search.
I would no longer configure Windchill in that way, but this may a different discussion 😉
Keep each released iteration is enough, but not any working iteration.
