Is There a Better Way to Convert Internal Components to External Components?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello,
I am looking for guidance on improving our design workflow.
We have multiple designers working on the same assembly. Some team members prefer creating internal components, as they allow easier sketch editing and offer certain workflow advantages. However, once the assembly is finalized, many of these components need to be converted into external components, since they are reused across multiple assemblies.
At the moment, I manually convert these internal components into external ones by the "Save Copy As" feature, but the issue is that those components are no longer linked with the parent assembly. I am wondering if there is a more efficient or recommended method to handle this process.
I have experimented with the Derive feature to convert internal components into external components. While this approach works, the main issue is that any change made to the parent assembly—even changes unrelated to the derived component—triggers update notifications in the individual component files. This quickly becomes disruptive and difficult to manage.
Is there a better way to convert internal components into external components while maintaining clean references and avoiding unnecessary update prompts?
Any guidance or best practices would be greatly appreciated. Thank you in advance for your help.