Are there any configurations that can be applied to prevent users from creating nested family tables? We've got something like 200 in Windchill now - hoping to prevent any new ones.
Besides the use of the employment severance policy?
I've created layered tables, where an assembly refers to a separate part that has its own table, but the nested ones I've seen no value in as they begin to be difficult to navigate. It doesn't seem to me to save much to do nesting, as there are just as many instances as a flat table for the same contents.
Have you tried a rolled up newspaper?
I may have to try the rolled up newspaper... LOL
From an old Cheech and Chong routine, sanitized:
"Bailiff, whack his fingers!"
I have not found one to prevent this.
If our users do this, we have failed in our training, or they failed to follow the protocols we set.
That said, I created the only nested table in the company back in 2000, with just under 150 instances. It has been rock solid, not one issue ever since, and we continue to build upon it.
I know our issues with nested family tables arise not from the software, but the people using it. Family Tables can be robust and trouble free and are a great technology when used correctly and for a fairly limited implementation.
The trouble starts when someone has to modify a nested family table and don't do it correctly.... And it can be hard to do it correctly.
Since most family tables are used for standard parts that don't change, except for adding new instances, at one company, I put them all in the Library and limited the editing to Librarians. If a user needed a new instance, they would email the librarian the request and then it would get added.