Skip to main content
MikeLockwood22-Sapphire I
22-Sapphire I
Mar 24, 2016 6:35 PM UTC
Question

Prevent nested family tables

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.


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

6 replies

dschenken2-Explorer
2-Explorer
Mar 24, 2016 11:54 PM UTC

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?

Translate
    mdebower18-Opal
    18-Opal
    Mar 25, 2016 12:18 PM UTC

    I may have to try the rolled up newspaper...  LOL

    Translate
      BenLoosli23-Emerald III
      23-Emerald III
      Mar 29, 2016 4:49 PM UTC

      From an old Cheech and Chong routine, sanitized:

      "Bailiff, whack his fingers!"

      Translate
        emetzger1-Visitor
        1-Visitor
        Apr 6, 2016 9:33 PM UTC

        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.

        Translate
        mdebower18-Opal
        18-Opal
        Apr 7, 2016 12:22 PM UTC

        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.

        IMHO

        Translate
        BenLoosli23-Emerald III
        23-Emerald III
        Apr 7, 2016 1:46 PM UTC

        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.

        Translate
          Terms & ConditionsAccessibility statement