Configuration Specific Properties w.r.t. Configs

[captaincaveman747]

I have found that if I create a second configuration of a simple block part.(Length x width x height), the Config Specific Properties that we (Company) use- Partnum and Partdescription values, seem to lock into the first configuration's values.
Example- Config A 1x1x4" Length Config B 1x1x10" Length.
When I show the config B in a SW B.O.M. it shows the values of the 4" Length. ** This seems new to me as previous versions I am sure that you could just change your length measurement by double clicking the dimension and changing it, and the BOM would adjust accordingly. Now with 2006 I will have to go into each new config and reassign the driving dimensions from the part? Doesn't make sense to me and will be very time consuming.

Captain Caveman
Almex Industries,Parry Sound ON.Canada\
SW2006,SP 0.0
Intel P4 3.0 Ghz,Quadro FX500,1 Gig Ram

 

[CorBlimeyLimey]

Do the dimensions update when you do a rebuild or update on the BOM?


Helpful SW websites every user should be aware of faq559-520
How to get answers to your SW questions faq559-1091

 

[captaincaveman747]

Rebuilds,Update of BOM,Re insert of BOM, no help! If I look at the second configuration's value/text expression values where I have selected them, they still show the first configuration's annotations. Example: It reads copied out as follows. - "D1@Sketch1@@0750-52" Length@FR10-110 Insulation.SLDPRT"
This is the last dimension driven value in the thickness x width x length values I pick from the part. See how it is still showing that it is pulling its value from 0750-52" Length configuration, which is a 3/4" Thick x 52" Long Piece. This annotation should read the value for the new cofiguration which is.3/4" x 64" Long.
The 52" Values were from the first config. I then added a configuration called 64" Length,then changed the length value accordingly. I should not have to then reassign(pick) the values again for each required dimension for my BOM. Help?




Captain Caveman
Almex Industries,Parry Sound ON.Canada\
SW2006,SP 0.0
Intel P4 3.0 Ghz,Quadro FX500,1 Gig Ram

 

[captaincaveman747]

I have found out the problem with the dimensional callouts for the various parts in a BOM. It seems that you can not name your configuration by using the "mark anywhere in the configuration name. It screws up the annotation callouts for the text/value properties. Relabelled the configuration as inch instead of "and it worked fine. Good riddance!


Captain Caveman
Almex Industries,Parry Sound ON.Canada\
SW2006,SP 0.0
Intel P4 3.0 Ghz,Quadro FX500,1 Gig Ram