Renamed Configurations in Assembly

[SuperMPG]

I renamed configurations in several parts and now whenever I open an assembly that refers to these part, I get a warning message complaining that it can't find the configs with the previous names so it will just use the defaults.

Does anyone know how I can tell SW to stop bugging me and just change the references to the configurations?

 

[ctopher]

Right-click on the part in the tree and change the config. Click on the top icon in the fly-out for 'Component properties'.

Chris
SolidWorks 09, CATIA V5
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

Update to at least SW2009-SP2. Renamed configs are automatically propagated to the associated assys.

 

[Eltron]

Yeah, that was a nice little change that they didn't really advertise in the SP 2 release.

Dan

http://www.eltronresearch.com

Dan's Blog

 

[SuperMPG]

@CorBlimeyLimey:

That would be a rather expensive fix, considering all seats would need to be upgraded from the current SW2007.

@ctopher:

I tried that, but when I open the Component Properties flyout it already lists the correct config name, so there's nothing to change it to.

The parts originally had a single config with a part number for the config name, but I changed the config name to Default to conform with all our other parts and our database standards. As it is, each part has only one config, and it's named Default. That's what I see in the Component Properties dialog; the only config listed is Default, which is correct and is the only option available. Yet even if I save the assy, the next time I open it I get the complaining message again about not being able to find the configs with the old name.

If SW2007 is too stupid to handle this simple change, so be it, but I really hope someone has knowledge of a way to force it to accept that the old config names are toast and stop bugging us about it (the engineers are grumbling).

Brian-

 

[CorBlimeyLimey]

Usually saving the assy after accepting the Default config was sufficient. I don't remember having to do anything else.

Maybe having all the referenced parts open, when opening and saving the assy, would help.

 

[SuperMPG]

Yes, it seems that the parts themselves need to be opened with write access as well as the assy and sub-assys. I was leaving the parts as read-only and opening the assys with write access but that wasn't working.

Thanks for the help, everyone.

Brian-

 

[ShaggyPE]

I have had this quirky error message pop up on a few files in the past. Primarily using 2006... its not everytime a config name got changed, just a a few specific assy files.

I think it is just something to live with.

-Dustin
Professional Engineer
Certified SolidWorks Professional
Certified COSMOSWorks Designer Specialist
Certified SolidWorks Advanced Sheet Metal Specialist