I'm not sure I'm following you. There was a change a couple of releases ago where you can delete components of a sub-assembly from a main assembly, but that doesn't sound like what you described. Can you explain a little bit more? I don't suppose you had two assemblies with the same name, did you?
I am confused on what it being described as well. It sounds like you have an assembly of parts, and you want to replace some of those parts with a subassembly. I don't see how SW would be deleting components from an assembly when it isn't open, but I would have to see your steps to really understand what's going on I think.
As far as a better way of achieving your goal, it sounds like using "Form new subassembly here" would solve your problem.
Are you sure the subassy was saved with the components added? Sounds like a stupid question - especially with the VAR remote driving... But more stupid things have happened to me. If I understand you correctly, this sounds like WRONG behavior - not intended functionality... I am sure I have done what I think you are describing and have never seen that behavior (although probably not yet in 2014...)
You say the subassy had never before been assembled to the top level? Then where is the connection? Are there a mess of assembly refs?
Please, let us know what you find,
Someone else creates assembly in one level -- no subassemblies. (The big dummy.)
I am asked to create a proper assembly drawing.
One group of parts should be listed as a subassembly.
I had already created this subassembly.
I delete the components I want to replace.
I insert the subassembly.
I open the subassembly file. It's empty.
I return to the higher level assembly and undo back to a point where all the parts show.
I open the subassembly file. It's all there.
I close SW, re-boot, and try again. Same results.
I call the VAR and am told this is supposed to happen. I find this hard to believe.
The sub that I've already created is used in several places, re-forming the assy would do more harm than good.
Is this clear enough?
Very clear - very strange - very stupid (if what she said is true.)
I would like to try it on my own.
That is not intended behaviour, and does not happen on my machines. I did exactly what you describe recently and the new sub-assy was not affected.
EDIT: I just repeated that scenario on another TL assy and, even with the sub-assy open, the components were not deleted.
Yes, that's clear enough, and no, that's not intended behavior, as others have said. Deleting components from one assembly shouldn't delete them from another assembly.
multiple contexts not checked.
not finding the "allow external refs" icon.
I am running SW2014 64 bit, SP 3.0.
external refs icon is only shown in a sketch when editing a part within an assembly.
As usual, Deepak rides over the hill in his white hat and six-shooters, to save the day by pointing out that I was not picking a subassembly (there were a couple) in the feature tree, but grabbing individual parts in the drawing view. The disaster that Andy points out is the issue at hand, and you can count me as one of the team that says that this is a terrible idea, and that all of the Cad Monkeys I work with have been bitten by it (They were just too proud to advertise their stupidity in a thead in the SW forum...).
Thanks for all the help.
The issue was that parts which Jim was deleting were components of a sub assembly was used in the top level assembly and another sub assembly which he wanted to insert in the top level assembly. So while he was deleting the parts, those were getting deleting from the sub assembly too and hence that was empty when opened up. The solution was to delete the sub assembly completely from the top level assembly.