Rename assembly (top-down design)-Error 1

[MartinHnv]

Hi!

I apologize when following problem explanation is confusing, it is apparently because i am confused.

I made assembly using top - down design, all parts are made in-context. Problems begun when I renamed assembly file, suddenly errors appeared. Each part external references are marked as "out of context". Also these references are still connected to assembly old name.
Does someone knows how to change these references to in-context ?

Actually i am not really sure that these errors are caused by renaming. I suspect that some errors appeared when I added driven dimensions to some parts BOM property (Lenght).

I added this assembly to attachment. I would be very happy when someone could help me.

 

[CorBlimeyLimey]

Did you rename within a Windows folder or SolidWorks Explorer?

 

[MartinHnv]

With explorer.

 

[MartinHnv]

Now an interesting message appeared when I tried to edit Part in-context. SW says :This part has features defined in the context of another assembly <assy2.sldasm>. You can edit the part, but cannot create external references to the components of the current assembly. I added picture from this message to attachment.

assy2 - assembly name before renaming

 

[rgrayclamps]

Hi, MartinHnv:

You did not indicate that you used SolidWorks Explorer. Most likely, you used Windows Explorer that caused the broken relations.

You need to use Solidworks Explorer, or alternatively, rename your SW documents using Save As with References in Solidwroks evironment.

Good luck!

Alex

 

[MartinHnv]

In previous message I mentioned that I used SW Explorer, I know that files must be renamed with this. Nevertheless in some reason external references remained out of update when I renamed my assembly. Why? and how to fix this so that references that are "out of context" would change to "in-context"?

 

[rgrayclamps]

Hi, MartinHnv:

The message (This part has features defined in the context of another assembly <assy2.sldasm>.) appears when you try to edit a part with an existing reference to different assembly.

If you rename your documents properly, this message will not appear.

If you really want to do this way, you need to enable "Allow multiple contexts for part when editing in assembly" in system option.

In your case, you don't want to do multiple contexts with your parts.

Good luck!

Alex

 

[CorBlimeyLimey]

A possible quick workaround/fix; (Note: I have not tried this)

1) Rename the assy back to its original name. If error message goes away, continue to step 2)
2) Use the Save as function to save the assy to a new name, but use the Virtual Components option to make all parts virtual within the assy.
3) Save as the assy to its final name, but make all parts "real".

 

[moon161]

You should get a warning if you have an ass'y w/ in context parts and you try to 'save as'. It should say that you have to reference each in context part to the new filename. Bit of a bummer.

 

[JMirisola]

And yet another reason to stay away from external references...

Jeff Mirisola, CSWP
Design Manager/Senior Designer
M9 Defense
My Blog

 

[CorBlimeyLimey]

moon161 ... not if the parts are virtual within the assy.

 

[drawoh]

MartinHnv,

I rename in-context assemblies all the time. When you rename the assembly, you must rename the in-context parts. This way, they remain in-context on your new assembly.

This makes sense. If you are leaving the old assembly intact and functional, those in-context parts should continue to be controlled by that assembly.

The parts that are not in-context can be left as is.

JHG

 

[MartinHnv]

Thanks CorBlimeyLimey !

I renamed assembly to old name and this warning

(This part has features defined in the context of another assembly <assy2.sldasm>. You can edit the part, but cannot create external references to the components of the current assembly. I added picture from this message to attachment)

disappeared.
Next I Saved As this assembly with different name, in "Save As with references" dialog box I checked "include virtual components". Now assembly with new name has all virtual components as in-context.

 

[MartinHnv]

Hi drawoh!

When exactly you rename in-context parts during assembly file renaming, within Save As in "Save As with references" dialog box or some other way?

 

[MartinHnv]

One more thought...

Renaming assembly that contains virtual components would be better option if it would only work. Now, I used Save AS option because renaming assembly with SW explorer did not fully work(in renamed assembly virtual components changed to out of context).
Is this means that renaming this kind of assemblys with SW explorer is not recommended or I still do not understand something?

 

[tristram]

My opinion is virtual components should be avoided.


-Joe
SolidWorks 2009 x64 SP 5.1 on Windows XP x64
8 GB RAM - Nvidia Quadro FX1700

 

[SnowCrash]

When you do this save as new assembly and rename or move everything to a new directory, be sure to get the drawings as well.
"how do I know? I just do"

--
Hardie "Crashj" Johnson
SW 2010 SP 2.1
HP Pavillion Elite HPE

 

[rgrayclamps]

Hi,

I agree with Joe. Virtual components are for quick concept.

Hi, MartinHnv:

You should be able to use SW explorer or SaveAs in SW to rename anything you want (while still maintain intended relations). You need to understand what happen behind the scenes completely before you can control them.

If you follow SolidWorks Help closely, you should not have any problems in renaming.

Good luck!

Alex