Right-click a feature, choose Parent/Child, and you see 12 children listed. Open Display/Delete Relations on the sketch — nothing. Enter Edit Feature — no explicit references to those children. Where are these relationships hiding?
This is one of the most common sources of rebuild failures and change-propagation surprises in SOLIDWORKS. Features that appear independent are connected through mechanisms that don’t show up in the usual places. This post maps every source of non-obvious parent/child dependencies and shows how to find and break them.
How Dynamic Reference Visualization Works
Dynamic Reference Visualization (DRV) draws arrows on the Feature Manager to show which features reference which. Enable it by right-clicking the top-level part or assembly name and toggling the two arrow icons in the context menu:
- Show Parent Relationships: draws blue arrows pointing toward the features your selected feature depends on
- Show Children Relationships: draws purple arrows pointing toward features that depend on your selected feature
A broken or dashed arrow with a box label means the referenced feature is collapsed in the tree or lives outside the current file (an external reference).
The key detail: DRV counts every reference type, not just sketch geometric relations. The Parent/Child dialog (right-click any feature > Parent/Child) gives the same complete list, sorted into parents and children, with the referencing entity named.
The Four Sources of Hidden References
1. Sketch Planes on Faces and Edges
When you draw a new sketch, SOLIDWORKS asks which plane or planar face to use. If you click a face on an existing feature, that feature becomes the parent — not through a geometric relation but through the sketch plane attachment.
Why it’s hidden: Display/Delete Relations only shows sketch segment relations (coincident, tangent, equal, etc.). The attachment of the sketch plane to a face is stored at the sketch level, not as a segment relation, so it never appears in that dialog.
Where to find it: In Edit Feature for the sketch, look at the Sketch Plane field at the top. It will show a face, plane, or edge name rather than a standard reference plane.
How to break it: Detach the sketch from the face reference by using Edit Sketch Plane (right-click the sketch > Edit Sketch Plane) and reselecting a reference plane (Front, Top, Right, or an explicitly created plane) instead of a face. This converts the implicit parent to a stable reference.
When this matters: A machining feature (pocket, counterbore) sketched on a cast surface. When the casting geometry is revised and that face changes position, every downstream sketch on it rebuilds — even sketches with no geometry touching the cast surface.
2. Through All, Up to Next, and Up to Body End Conditions
A Boss-Extrude or Cut-Extrude set to Through All terminates against whatever geometry currently occupies that direction. SOLIDWORKS resolves the actual termination face at rebuild time and registers that face as a parent.
Why it’s hidden: The feature definition shows the end condition type (Through All) but not the resolved face. After a rebuild, the parent/child dialog will list the feature whose face absorbed the termination as a parent — but that face name won’t appear in the sketch relations or in the feature’s explicit selections.
The same applies to:
- Up to Next: terminates at the next face in the extrude direction
- Up to Vertex: references a vertex by selection (explicit, visible)
- Up to Surface: references a surface body (explicit, visible)
- Through All — Both: adds parents on both sides
How to find the resolved face: hover over the termination face in the graphics area while the feature is in Edit Feature mode. SOLIDWORKS will highlight the resolving geometry.
How to break it: Change the end condition to a blind depth with an equation or global variable. This eliminates the face reference at the cost of requiring an explicit depth value. For Through All cuts that genuinely need to go all the way through, the parent relationship is usually acceptable — just document it.
3. Equations and Global Variables
A dimension value of "D1@Sketch3" = "D1@Sketch1" + 5 makes Sketch3’s D1 dimension a child of Sketch1. This is visible in the Equations dialog (Tools > Equations) but does not produce a geometric relation, so Display/Delete Relations reports nothing.
Why it matters: Equations can create long dependency chains across features, bodies, and configurations. A single global variable used in 15 features means changing that variable triggers 15 feature rebuilds. DRV will draw 15 child arrows on the driving feature — seemingly unrelated.
Where to see them: Open the Equations dialog. The Linked Values column shows which dimension drives which. For configurations, each configuration maintains its own equation set.
How to find equation parents programmatically:
Dim swApp As SldWorks.SldWorks
Dim swModel As SldWorks.ModelDoc2
Dim swEqMgr As SldWorks.EquationMgr
Sub ListEquationParents()
Set swApp = Application.SldWorks
Set swModel = swApp.ActiveDoc
Set swEqMgr = swModel.GetEquationMgr
Dim i As Integer
For i = 0 To swEqMgr.GetCount - 1
Debug.Print swEqMgr.Equation(i)
Next i
End Sub
This prints every equation, including cross-feature dimension references. The left side is the child, the right side expression shows the parents.
4. Pattern Seed and Component References
Linear and circular patterns, mirror features, and curve-driven patterns reference their seed feature or pattern parameters. These create parent/child links that appear in DRV but not in any sketch relation dialog:
- Seed feature: the body being patterned is a parent of the pattern feature
- Pattern direction: a linear edge or axis selected for direction is a parent
- Instances count driven by equation: the equation target is a parent
Mirror features are similar: the mirroring plane and every seed feature are parents. Change the plane and all mirrored bodies rebuild.
Delete/Keep references: when you suppress or delete the seed feature, SOLIDWORKS offers to keep the pattern instances as a separate solid. This breaks the parent dependency at the cost of losing parametric control.
The Faster Diagnostic: Parent/Child Dialog
Right-click any feature in the tree and choose Parent/Child. The dialog splits into two tables:
| Column | Meaning |
|---|---|
| Parents | Features this feature directly depends on |
| Children | Features that directly depend on this feature |
For each entry, the Entity column names the specific reference (a sketch segment, face, edge, plane, dimension, or equation variable). This is the fastest way to understand what specifically connects two features without having to interpret DRV arrows.
The dialog shows one-level deep. If you need to trace a full dependency chain, you have to open it repeatedly for each intermediate feature.
Breaking References Without Rebuilding From Scratch
Once you’ve identified the reference, the options in order of surgical precision:
- Edit Sketch Plane: reassigns the sketch to a reference plane rather than a face, breaking the face parent without modifying the sketch geometry
- Delete Sketch Relation: for explicit geometric relations shown in Display/Delete Relations, delete the specific constraint creating the link
- Change equation to inline value: replace a cross-feature equation with a fixed value or global variable not tied to another feature’s dimension
- Make Derived: for configurations, use a derived configuration to isolate the overrides rather than embedding them in the base equation set
- Absorb into body: for Through All cuts, change to a blind depth with an equation referencing overall body height — this replaces the face parent with a cleaner numerical dependency
What the 12-Children Scenario Usually Means
When DRV shows far more children than you’d expect, the most common cause is a heavily-used reference plane or sketch. A sketch drawn on Face1 of a base extrude, with 12 subsequent features sketched on that same face, creates exactly 12 children on the base extrude — all of them via sketch plane attachment, none of them visible in Display/Delete Relations.
The fix is almost always the same: replace the face reference with an explicit plane. Create a plane offset from the face at the time it was created, or use the existing Front/Top/Right planes as the attachment. Future features then reference the plane (which is stable) rather than the face (which can move).
This is particularly important before running batch DXF exports or automated rebuild pipelines — unexpected parent/child chains are a major cause of rebuild errors in headless/macro automation where you can’t respond to interactive error dialogs.
Related Patterns in Assemblies
The same concepts apply in assemblies but through different mechanisms:
- Mate references: a component mated to a face of another component creates a parent dependency on that face
- In-context references: a part modeled in context of an assembly references the driving geometry in the parent assembly — visible via Edit > List External References
- Derived configurations: a dependent configuration borrows suppression state from its parent
In-context references deserve a separate post — they are the assembly equivalent of the sketch-plane-on-face pattern, and managing them across design changes is one of the more complex areas of SOLIDWORKS practice. If your SolidWorks workflow automation hits unexpected errors when processing assemblies non-interactively, check for unresolved in-context references first.
The parent/child system in SOLIDWORKS is intentionally implicit — you model geometry and relationships form automatically. The cost of that convenience is occasional invisible connections between features that appear unrelated. The diagnostic path is: Dynamic Reference Visualization for a visual overview → Parent/Child dialog for the specific entity → Edit Feature / Edit Sketch Plane / Equations to understand the mechanism → targeted fix to replace the implicit reference with a stable one.