Conflicting Hierarchy Logic between Model Browser and Part Browser

Chaitanya_

I'm noticing a discrepancy in how HyperMesh organizes entities and would like to know the "Source of Truth" for the hierarchy.

Import type: BOM

• In the Model Browser: I see Parts with a subsystem of part-assemblies. (Note: I'm also hitting a bug where Assembly & Parts section expansion is limited/truncated here).
• In the Part Browser: The hierarchy shows Assemblies → Sub-assemblies → Parts. But in other areas, it shows Parts → Components.

If Assembly is technically the higher-level organizational entity, why does the Model Browser use "Parts (X)" as the primary root header? This creates significant confusion, especially when the Part Browser then shows Assemblies as the parents of those Parts.

It feels like the UI is mixing two different logic systems:

1. A CAD-style hierarchy (Assembly > Part)
2. A CAE-style hierarchy (Part > Component)

Does anyone have a best practice for explaining this to new users, so they don't get lost in the nested expansion? Also, is the "limited expansion" bug in the Model Browser a known issue when the Part count gets too high?

Jason_Craanen

Think of the Model Browser as the Table of Contents (TOC) of your model — it lists all entities, but doesn’t always reflect the CAD hierarchy.
Use specific entity browsers, like the Parts Browser, to visualize and work with the actual entities in context.
Also note that nomenclature is being standardized: Components and Classic Assemblies will eventually be removed, in favor of Parts / Part Sets / Part Assemblies.