Skip to main content
A
akelly12-Amethyst
12-Amethyst
January 17, 2020
Question

Family table headings of varied items from inheritance

  • January 17, 2020
  • 3 replies
  • 2985 views

TL/DR: If you make a family table of dimensions varied from an inheritance feature, the column headings are funky - how to rename?

 

Follow me a bit ... Thought I had a brilliant idea.  We have two parts that are kind of similar.  Both of them have family tables.  Not similar enough that I want to throw everything into a single .prt with one big family table. But 90% of what's there is common.  So why not use inheritance to share the common geometries??

 

So I picked part "A" as the master part.  "A" has a family table.  Created a new "B" part by inheriting "A".  Added Varied items to the inheritance feature so I could suppress "A"'s features not needed in "B" and have some "B" dimensions different from "A".  So far, so good.

 

"B"'s new dimensions also need to be tabulated, so I added the dimensions to "B"'s family table.

 

Family table column headings make no sense.  In the inheritance feature's varied items, the dimension name shows as "P" (same as I renamed in "A"), but in the family table, it shows up as "IN_D_298:FID_2441 D298[2441]". Expected result: column heading in the family table editor would display "T1", "T2", "S", "R", "P", "W" like they do in varied items. See pictures.

 

If I drill into the the inheritance feature and edit dimensions, the dimension names show up as "T1", "T2", "S", "R", "P", "W".  So I can't change the column headings (dimension names) the "normal" way.

 

Work around is to create parameters in "B" with the right names, then use relations to change the varied items.  I might need to keep the silly column names to actually get the instances to regenerate with the right dimension values.  Surely there's an easier way.

 

Varied Items.pngFamily Table.png

    3 replies

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    January 17, 2020

    How often will the common features/parameters/dimensions change? If they are mostly static, copy the family table to the other and you eliminate the funky names.

    Those funky names do not surprise me as your B part is using the inheritance features, not real features and that funky name is the internal name link to your A part.

     

    P
    Pettersson15-Moonstone
    15-Moonstone
    January 22, 2020

    How about using a comment row to indicate the "true" name of the dimensions? Ideally, you'd want it at the top, but Creo annoyingly doesn't allow a comment row above the generic (which is where I've wanted my comment row 100% of the time I've used the functionality). But you could place one just below the generic and write the real names of the columns.

    B
    BK_99154701-Visitor
    1-Visitor
    February 7, 2022

    We have the same issue. I think, the suggested workarounds are known. But nevertheless there must be a reason, why this topic is opened. Sure, we all could use the workarounds, but maybe we do not want to? We all know, what PTC likes: New and fancy features. Boring 2d-drawings are neglected, because it's not sexy enough.

    I can't believe, that this requested feature is impossible to program. And if so, PTC could at least explain it.

    S
    sacquarone21-Topaz I
    21-Topaz I
    February 7, 2022

    Hello @akelly and @BK_9915470 

     

    The impossibility to rename headers of Family Table columns is a current limitation of Creo Parametric, effective whatever the version used. The headers are always supposed to show the identifiers, and they are populated in an hardcoded way (not drivable by any config.pro option).

     

    Considering above limitation, I can nevertheless try to provide some guidance to gather in the Varied Items table to "good and relevant information" which can be observed later in the column(s headers od the family tables.

    => This can be done essentially thanks to Assoc.Param column, and helpful also the owner column.

     

    I recorded a movie with sound attached to this post to propose guidance in this direction.

     

    Note: I'm perfectly aware that this is not a "perfect solution", but it's nevertheless the only guidance coming into my mind to help you improving ergonomy of our tools to give an answer (probably useful, but far from being perfect) to this business need.

     

    Hope this will help you anyway.

     

    Regards,

     

    Serge

      A
      akelly12-AmethystAuthor
      12-Amethyst
      February 7, 2022

      Thanks for the video.  Unfortunately, the weird column headings don't provide mistake-proofing to the user that's maintaining the family table.  And the column headings aren't usable in a 2D repeat region in a drawing (e.g. to make a PDF / print of the tabulation).

      Terms & ConditionsAccessibility statement