this happens a lot, if I delete a sub assembly or part from an assembly, sw deletes the components from the original assembly or part file as well. how can I delete things without messing with the original?
The wording of your problem has me confused. Can you expound on what you are doing and what is then happening?
What do you mean from the original? If you delete a part or a subassy from an assy, it's deleted from that assy.
Can you show an example of what you are talking about? I'm not sure that I understand either.
one example is hardware assemblies, nut, bolt and washers. I bring them in as an assembly called .375 hardware. sometimes I delete them and use something else. the next time I insert .375 hardware all of the components are not found, I have to browse for them. I'm not sure if it only happens if I delete from the tree or the graphics area.
If you have in context part relation then yes deleting a sub-assembly or parts can wreak havoc.. If that happens a lot, then I would like to suggest changing your workflow.... In any design you should be able to delete any item in the feature tree and the only errors you get is mating errors, because of missing faces or points etc..
If you're selecting a component of a sub-assembly in the graphics area and choosing "Delete" you should be getting this message:
If you're not then you might want to check your dismissed messages.
There was an "Enhancement" a few years ago that allowed deleting of sub-assembly components without actually choosing the sub-assembly and choosing the "Edit component" icon, even if users intent was to delete the sub-assembly from the upper level assembly. It created a lot of unintended consequences, and wreaked havoc with a lot of people's sub-assemblies. The above message was introduced to address the issue.
I like this feature. I also like the dialog that is offered to make sure one is sure of what they are deleting.
I like the flexibility that it offers in development.
It was more fun before they came up with the confirmation dialog box.
I'm more stern about things because I expect that my users will pay attention to the selections. I also save a lot so as to not lose information. We also use vault; an undone check-out or not checked out sub-assembly really helps to not mess up as well...
If I understand your question, yes SW made a horrible change a few releases ago.
It used to be if you tried to delete anything in a sub assembly, you simply deleted the whole sub assembly.
That's what the dialog box shown above is supposed to recreate.
But you can also do all sorts of fun stuff like suppress things in the sub assembly that aren't supposed to be and when you save the change sticks. And you get no warning box telling you that it happened.
I've destroyed a few assemblies till I learned what was going on. And I've run across many other assemblies that others have destroyed that I bet they were blissfully unaware and saved away.
My practice is to either delete the subassembly as whole (never its components unless that is the change I want for the sub everywhere it is used).
If you only want some of the components of a subassembly then either make a configuration of that sub that has the unwanted components suppressed OR dissolve that subassembly into the main and then delete and regroup to your heart's content.
OH it's a whole 'nother ball game when the assemblies have been released... Then it's lock down city.
Understood and agreed! I am doing so much far upstream development that I have the option to create a lot of subassemblies for their grouping convenience. When the project moves into release those subs get dissolved into the main assembly.
Retrieving data ...