Assembly Operations That Create Dependencies
Dependencies are created in a number of operations. You can break these dependencies in the Reference Viewer without causing the assembly to fail.
Substituted Components
When you substitute a component in a simplified representation, it is added to the assembly. When the simplified representation is deleted without deleting the substitute component , it remains a ghost object in the assembly and maintains its dependency on the substituted component. You can delete an unused substitute component by deleting all its dependencies. Point to the component in the Reference Viewer and a Tooltip states wether or not the component in the assembly is in use.
Data Sharing Features
Data sharing features copy data from a reference model to a target model. A dependency is created on the referenced model. You can break dependencies in the following circumstances:
• An independent DSF—When you set a copy geometry, merge, inheritance, or Shrikwrap feature to independent.
• Mirrored merge—When you use the Mirror command in the assembly context. A merged feature is created. You can set this feature to be independent.
• Merged part—When you create a merged feature by merging parts. You can set this feature to be independent.
• Unused reference model—When the data sharing feature is redefined to reference a different model. Data relevant to the original model is still stored with the DSF and a nonrequired dependency is maintained.
Notebooks
When a model is driven by a notebook, a dependency is created between the model and the notebook. When you break the dependency between them, the model becomes independent of the notebook.
Interchange Assemblies
When an assembled component is member of an interchange assembly, a dependency is automatically created to the interchange assembly.