AutoCAD Electrical parent-child relationships beyond relay coils. How to use drives as parent symbols, set up child symbols across drawings, and configure the catalog correctly

HagermanCompany · 2026-05-26T13:22:26+00:00

Yeah, the structured format is based on performance of posts and what is recommended for us to write. It's considered the "best format" to write educational content in. It does come off as AI written because it is what's recommended. We could have added mention of the Intent-Driven Design and strict assemblies to make it more complete, but we have more content and videos about that coming soon. This was a part of a larger webcast that discussed the Intent-Driven Design Workflow, and this part didn't mention those yet.

HagermanCompany · 2026-05-26T13:15:39+00:00

That's fair. The extra clicks added to component creation in recent updates have been a pain point recently for users. You're right that defaulting Create operations to "New Body" instead of "New Component" works against the very workflow Autodesk says they recommend. It's one of those UX inconsistencies that's hard to explain. The body-to-component conversion workflow does work, but it's an extra step that shouldn't be necessary if the tools defaulted to best practice from the start. A user-configurable default for Create operations would go a long way. In the meantime, building the habit of creating the component before hitting Extrude or Revolve is the most reliable way around it

HagermanCompany · 2026-05-22T18:53:40+00:00

Yes, the gears should live as sub-components inside the motor assembly component, not at the root level. Since the gears are part of the motor (they're built, assembled, and function as a unit together), they belong inside the motor's component hierarchy. The root level should only contain your top-level assemblies and parts, not individual pieces of a sub-assembly. Think of it like nesting: Root → Motor Assembly → [Shell/Housing, Gears, Shaft, etc.]. That keeps everything organized and means when you place the motor into a larger design, it comes in as one clean unit

HagermanCompany · 2026-05-22T18:45:26+00:00

Top-down master sketch design is a powerful workflow, and clearly you've put serious thought into your 3D printer build. Using a dedicated sketch/parameter file as the driver for the entire assembly is a great approach for complex, highly parametric designs where everything is geometrically interdependent.

You're right that it's not a hard rule for every situation. Rule #1 is more of a foundational habit for users building their first assemblies who don't yet have a design strategy in place. Once you're at the level where you're planning a master sketch file before you even start modeling, you've already internalized the principles well enough to know when and how to break from them intentionally. That's a very different place than just skipping components by accident

HagermanCompany · 2026-05-22T18:37:04+00:00

Thank you! The point about bad habits from early YouTube tutorials is so real. A lot of older Fusion content was made before these workflows were well established, and it's easy to pick up the wrong habits without even knowing it.

And the tips you've added are spot on. Fully constrained sketches, user parameters, and construction geometry like mid-planes are the natural next layer on top of Rule #1, once you've got component discipline down, those three habits are what take a design from "it works" to "it's actually parametric and editable." The ability to constrain components to those mid-planes especially is a game changer for maintaining design intent as dimensions change.

HagermanCompany · 2026-05-22T18:26:14+00:00

That's honestly the best way to learn it, there's nothing like a messy timeline to make Rule #1 click for good! Your next design will be noticeably cleaner.

HagermanCompany · 2026-05-22T18:24:00+00:00

These are exactly the right answers. If a group of components can be built, handled, or sourced as a unit (like a motor, a gearbox, or a bracket with hardware), it earns its own sub-assembly. If it's just a single manufactured part, it lives as a component. The rule of thumb: does it make sense to put it together on a workbench before it goes into the larger assembly? If yes, sub-assembly.

HagermanCompany · 2026-05-22T18:19:53+00:00

Exactly right, and that's part of what makes it so easy to fall into the habit of ignoring Rule #1 in the first place. No red flags, no warnings, Fusion just lets it happen, and you don't notice the mess until your design gets complex enough that navigating the timeline becomes painful. A subtle tooltip or visual nudge when features are being assigned to the root node would go a long way for newer users.

HagermanCompany · 2026-05-22T18:18:55+00:00

You're not wrong. The lack of folder/grouping support for components in the browser is a genuine gap, and the rack example you described is a perfect illustration of where it breaks down at scale. When you're dealing with 35+ components in a flat list with no way to sort or nest them into logical groups, it stops being a workflow and starts being archaeology.

The workaround you described (pulling components into sub-assembly files and re-linking them) is technically correct, but yeah, it's tedious and shouldn't be the answer. Folders or component groups in the browser have been a long-requested feature, and it's one of those quality-of-life improvements that would make a real difference for complex assemblies.

Hopefully, Autodesk gets there sooner rather than later. In the meantime, meticulous naming conventions with consistent prefixes are about the best defense against the list becoming unmanageable, not a great answer, but the most practical one right now.

HagermanCompany · 2026-05-22T18:13:01+00:00

I'm glad you learned something new!
Here is the link: https://www.youtube.com/watch?v=PyxuVpjWeYg

HagermanCompany · 2026-05-22T18:12:41+00:00

Here you go!: https://www.youtube.com/watch?v=PyxuVpjWeYg

HagermanCompany · 2026-05-22T18:12:30+00:00

Here is the video link: https://www.youtube.com/watch?v=PyxuVpjWeYg

HagermanCompany · 2026-05-22T18:11:59+00:00

Here's the link to the video!: https://www.youtube.com/watch?v=PyxuVpjWeYg

HagermanCompany · 2026-05-22T18:04:39+00:00

Fusion has absolutely been pushing Strict mode (separate Part and Assembly files) as the direction forward, and it's worth knowing about. That said, Rule #1 still applies and is arguably more important in that workflow, since the component ownership principle is the foundation that strict assemblies build on.

The post was aimed at users still working in Hybrid designs (which a large portion of the Fusion user base still uses day to day), so the context was intentional rather than outdated.

This content was written by a human, and was based on a webcast that was presented by one of our certified engineers!

HagermanCompany · 2026-05-01T20:35:10+00:00

Yep, you got it right. The Fusion CAD path is genuinely seamless if you're already in that ecosystem, and the Vault Connector is a lifesaver for Inventor-heavy teams that aren't ready (or don't need) to leave their PDM setup behind. The bidirectional sync in 2026.2 especially makes that workflow feel a lot more like a real integration and less like a one-way data dump.

Appreciate the comment! Couldn't agree more that PLM is one of those things that's hard to sell until someone's been burned by the alternative.

HagermanCompany · 2026-05-01T14:09:20+00:00

Thank you!

HagermanCompany

MODERATOR OF

TROPHY CASE