Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
Configuration Description in BOM? 1
- Thread starter sdb999
- Start date
Try using configuration-specific custom properties.
For instance, if you have a custom property for "description", have a configuration-specific custom property for "description", as well. If I'm not mistaken, the configuration-specific property will override the "universal" property.
![[bat]](/data/assets/smilies/bat.gif "[bat] [bat]")
Good and evil: wrap them up and disguise it as people.
For instance, if you have a custom property for "description", have a configuration-specific custom property for "description", as well. If I'm not mistaken, the configuration-specific property will override the "universal" property.
Good and evil: wrap them up and disguise it as people.-
1
- Thread starter
- #3
That won't display configuration description, only the value of the custom property called "description". I have no desire to enter this information twice. Once for the feature tree and another for the BOM, title block and notes. Although that's what I'm doing now it's a total pain!
Sounds like you need to make a special BOM as well, that would link to the Custom property.
Regards,
Scott Baugh, CSWP![[wiggle]](/data/assets/smilies/wiggle.gif "[wiggle] [wiggle]")
![[alien]](/data/assets/smilies/alien.gif "[alien] [alien]")
3DVision Technologies
faq731-376
When in doubt, always check the help
Regards,
Scott Baugh, CSWP
3DVision Technologies
faq731-376
When in doubt, always check the help
- Thread starter
- #6
Great idea, but I need PRP:"SW-Configuration Description" and that variable does not exist. If it did I wouldn't have an issue. Basically I have multiple parts in one file. Let's say they're washers each with a unique part number (Config. Name) and Description (Config. Description). The part model file looks great, users can see the most important info. with no right-click property nonsense, and there is no need for extra cust/config. specific properties. Now make a drawing and it hits the fan! You can link the config. name all day, but description is MIA. Bug?
Try this:
Create a note within the part. In the note, go to the property manager and click the "link to property" button. Insert the property "SW-Configuration Name". Copy the text that is inserted which reads, $PRP:"SW-Configuration Name". Create a new custom property and paste $PRP:"SW-Configuration Name" into the value of that property.
Honestly, I'm not 100% sure how this will get reflected in the BOM, but it's something to go with.
Good and evil: wrap them up and disguise it as people.
Create a note within the part. In the note, go to the property manager and click the "link to property" button. Insert the property "SW-Configuration Name". Copy the text that is inserted which reads, $PRP:"SW-Configuration Name". Create a new custom property and paste $PRP:"SW-Configuration Name" into the value of that property.
Honestly, I'm not 100% sure how this will get reflected in the BOM, but it's something to go with.
Good and evil: wrap them up and disguise it as people.The Description you are entering in at the Configuration stage is for Clarification of Parts and assemblies not for drawings. Because if you RMB the file name in a part or assembly you get this option in that menu "Tree Display". If you follow that path you get the option of viewing "Show Configuration Description".
IMO what I'm about to tell you much easier than what your doing now.
You should be using "Configuration specific" like Tick points out above.
Start a new part and save 2 configs to it and name them however you want but don't add the config names there. Make and assembly and place that part in there. Save it and start a new drawing.
Go back to your part and...
1) Go to File\Properties
2) Config. specifc tab
3) Pick Description
4) Type in the value (Name)
5) Click enter
6) Do this for both Configs.
7) go back to your Drawing
8) Insert your BOM using the standard BOM temp file.
9) You should see the description in the BOM.
If you make 2 configs in your assembly and set up those configs using the 2 different part configs. You will be able to switch between the configs in the drawing. Then the BOM will update according to the config being used.
If you need an example let me know
Regards,
Scott Baugh, CSWP
3DVision Technologies
faq731-376
When in doubt, always check the help
IMO what I'm about to tell you much easier than what your doing now.
You should be using "Configuration specific" like Tick points out above.
Start a new part and save 2 configs to it and name them however you want but don't add the config names there. Make and assembly and place that part in there. Save it and start a new drawing.
Go back to your part and...
1) Go to File\Properties
2) Config. specifc tab
3) Pick Description
4) Type in the value (Name)
5) Click enter
6) Do this for both Configs.
7) go back to your Drawing
8) Insert your BOM using the standard BOM temp file.
9) You should see the description in the BOM.
If you make 2 configs in your assembly and set up those configs using the 2 different part configs. You will be able to switch between the configs in the drawing. Then the BOM will update according to the config being used.
If you need an example let me know
Regards,
Scott Baugh, CSWP
3DVision Technologies
faq731-376
When in doubt, always check the help
- Thread starter
- #9
We've hit on two issues which are giving my company absolute fits.
1. There must be two or more configurations of a part before Tree Display works in an assembly, and it's limited at that.
2. Two different unlinkable (is that a word) fields must be populated with part description. One for the part model(config. desc.), and one for drawings(cust. prop.).
If I was an island or small work group without a PDM this would not be as much an issue. Fifty+ users at two locations installed with Smarteam PDM interfaced with SAP ERP in manufacturing and procurement and the nightmare is just beginning.
All these solutions work and are greatly appreciated, however they are all work arounds for one glaring short coming of SolidWorks: Complete access to all system variables is not available to system integrators.
What I was hoping from this post was the hack-under-the-hood method to get at Configuration Description from the $PRP"system variable" level. It's there, we see it we just can't read it, and 2004 B2 looks no better. If anyone knows of an individual or organization that may have expertise in this area please let me know. Thanks again all.
1. There must be two or more configurations of a part before Tree Display works in an assembly, and it's limited at that.
2. Two different unlinkable (is that a word) fields must be populated with part description. One for the part model(config. desc.), and one for drawings(cust. prop.).
If I was an island or small work group without a PDM this would not be as much an issue. Fifty+ users at two locations installed with Smarteam PDM interfaced with SAP ERP in manufacturing and procurement and the nightmare is just beginning.
All these solutions work and are greatly appreciated, however they are all work arounds for one glaring short coming of SolidWorks: Complete access to all system variables is not available to system integrators.
What I was hoping from this post was the hack-under-the-hood method to get at Configuration Description from the $PRP"system variable" level. It's there, we see it we just can't read it, and 2004 B2 looks no better. If anyone knows of an individual or organization that may have expertise in this area please let me know. Thanks again all.
![[smile]](/data/assets/smilies/smile.gif "[smile] [smile]")
Look SW has other ways of getting what you want. If you don't want to do it this away (suggestion above) I give could another way, but you wouldn't be happy with it either. So there isn't much more I can tell you.
Yes you can see it in the configuration properties and you might be able to get to through API, but that's WAY more trouble than you doing in the above fashion.
Sounds like you just need to put in an Enhancement request or call your VAR and tell him what you think about it.
1. There must be two or more configurations of a part before Tree Display works in an assembly, and it's limited at that.
Enhancement Request
2. Two different unlinkable (is that a word) fields must be populated with part description. One for the part model(config. desc.), and one for drawings(cust. prop.).
Enhancement Request
Other ideas:
You could change the box at the bottom so you BOM well use the Config name as the part number, then make a custom BOM.
or
You could use a DT then you could use the "$PRP@Descriptions" easier and custom control your models.
But I think what your after is not going to be achieved easily and your going to either have to bit the bullet and try one of these ways, or Pay some API guru the big bucks to get that information into a BOM, or keep typing it in X amount of times.
Regards,
Scott Baugh, CSWP
3DVision Technologies
faq731-376
When in doubt, always check the help
Yes you can see it in the configuration properties and you might be able to get to through API, but that's WAY more trouble than you doing in the above fashion.
Sounds like you just need to put in an Enhancement request or call your VAR and tell him what you think about it.
1. There must be two or more configurations of a part before Tree Display works in an assembly, and it's limited at that.
Enhancement Request
2. Two different unlinkable (is that a word) fields must be populated with part description. One for the part model(config. desc.), and one for drawings(cust. prop.).
Enhancement Request
Other ideas:
You could change the box at the bottom so you BOM well use the Config name as the part number, then make a custom BOM.
or
You could use a DT then you could use the "$PRP@Descriptions" easier and custom control your models.
But I think what your after is not going to be achieved easily and your going to either have to bit the bullet and try one of these ways, or Pay some API guru the big bucks to get that information into a BOM, or keep typing it in X amount of times.
Regards,
Scott Baugh, CSWP
3DVision Technologies
faq731-376
When in doubt, always check the help
- Thread starter
- #12
Our VARs, SolidWorks Major Account Manager, and myself submitted this as an enhancement request some time ago. We're obviously not alone just more affected by it.
I only turn to this forum after I've exhausted all the VAR and SolidWorks Corporate avenues, as I've found the users often know more about the software than those who sell it. Thanks for all the effort, if I find a solution I'll post it.
I only turn to this forum after I've exhausted all the VAR and SolidWorks Corporate avenues, as I've found the users often know more about the software than those who sell it. Thanks for all the effort, if I find a solution I'll post it.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question