Skip to main content
B
Boris_w_374-Participant
4-Participant
July 8, 2026
Solved

Updating inheritance file path?

  • July 8, 2026
  • 4 replies
  • 86 views

I’m testing out a multibody part design workflow.

Everything seems to work well except for the link to the source model.

If the source model is moved or renamed, the child models regenerate but I can’t find a way to reestablish the link. Any suggestions?

My workflow.

  • Create multibody part.
  • Import the multibody part into a new (empty part) using inheritance. This brings in solid bodies and datums.
  • Do “keep bodies” to keep just the single body that is necessary.
  • Repeat for other bodies.
  • Close parent and child parts, erase from session.
  • Rename or move parent part.
  • Open one of the child parts and try to re-link.
Best answer by tbraxton

This assumes you are not working within a Windchill managed environment.

Dealing with the name of the master model is readily dealt with assuming you have a copy of the model that is inclusive of the required references used to drive the derivative components. You need to know the name of the model that the derivative part is looking for when updating the external references. You then must rename the “master” model with the exact name that was used originally. Once this model is named appropriately you then need to bring it into session (clear from session all parts first) and then open the derivative components. You can then update the external copy geometry features etc. and they will update assuming there are not issues with the parental references in the master model.

If you want to change the name of a master model and propagate that change to all derivative models, then you need to make sure that you have all models that a derived from it in session when renaming the master and then saving a copy of all of the models so that the new master name is saved with all of the derivative parts.

When I get more time, I will respond to the use of inheritance features vs merge or copy geom etc.

4 replies

tbraxton
tbraxton22-Sapphire II
22-Sapphire II
July 8, 2026

Your query is not clear, but it seems that the source of your issue is that you are renaming or moving parent models such that they are not in session when you want to use them to drive derivative models. If the parent object is not in session, then Creo will not use it to regenerate derivative (children) models.

You would be better served by explaining at a high level what design intent you are managing via the inheritance feature(s) and how you want to control it in the context of a Top-Down Design approach.

Why are you bringing in all bodies and only “keeping” a single body using inheritance functionality? You can create part from body for any single body (no inheritance feature needed for this). If you need the inheritance to manage something, then explain in detail why you are using that.

    B
    Boris_w_374-ParticipantAuthor
    4-Participant
    July 9, 2026

    explaining at a high level what design intent you are managing via the inheritance feature(s) and how you want to control it in the context of a Top-Down Design approach.

    New to Creo, so all ears for best method. 15yrs of SolidWorks.

    Design intent:

    Let’s say I’m designing a box that contains body+lid.

    I create a multibody “master part” that defines overall physical geometry for the two bodies.
    Instead of fully detailing out body+lid in master, I create datum features that will drive position of features in individual parts.
    So datum points mark location of clearance holes in the lid and threaded holes in the body.

    Then I want to create individual files for the body and lid and import the solid and datum features from master.

    What I’ve tried:

    • “Create part from body” in multibody master works. Imports solid features. References though need to be selected one by one. So if I have a 8 datum point bolt pattern, need to select 8. If I later change the bolt pattern to 10 holes in master, need to re-edit the copy external geometry feature.
    • Same thing with “publish geometry”. Need to select individual references one by one.
    • Merge/Inheritance gives me ability to import all from master, solids and datums. Remove body allows “keep selected” so just pick the one I want to keep. All datum data gets imported and is fully updated from “master”. The only challenge I haven’t fixed is how to update the link if “master” gets renamed to “master2”.

    As I’m testing out the process I want to make sure it is robust and problems can be fixed down the road before I implement it on the real model. Thus want to know how to update the link to “master” if “master” is accidentally or purposely renamed.

     

    Thank you,

    Boris.

    tbraxton
    tbraxton22-Sapphire IIAnswer
    22-Sapphire II
    July 9, 2026

    This assumes you are not working within a Windchill managed environment.

    Dealing with the name of the master model is readily dealt with assuming you have a copy of the model that is inclusive of the required references used to drive the derivative components. You need to know the name of the model that the derivative part is looking for when updating the external references. You then must rename the “master” model with the exact name that was used originally. Once this model is named appropriately you then need to bring it into session (clear from session all parts first) and then open the derivative components. You can then update the external copy geometry features etc. and they will update assuming there are not issues with the parental references in the master model.

    If you want to change the name of a master model and propagate that change to all derivative models, then you need to make sure that you have all models that a derived from it in session when renaming the master and then saving a copy of all of the models so that the new master name is saved with all of the derivative parts.

    When I get more time, I will respond to the use of inheritance features vs merge or copy geom etc.

      tbraxton
      tbraxton22-Sapphire II
      22-Sapphire II
      July 9, 2026

      Here is an old article that was written when the inheritance feature was added to Pro/E (24+/- years ago). It is dated but the information is still valid. It explains most of the differences to using merge and copy geom.

      Note that multibody was added recently so that is not addressed here. The files are HTML so you will need to open them in a browser.

        Terms & ConditionsAccessibility statement