AnsweredAssumed Answered

Using Configuration Description in Assembly Design Table

Question asked by Brent Van Camp on Aug 20, 2010
Latest reply on Aug 20, 2010 by Brent Van Camp

Like • Show 0 Likes0
Comment • 9

I have a complicated assembly with multiple configurations which call out specific component configurations in the BOM. For that reason, I'm using my assembly design table as a sort of makeshift BOM so that I can link the component configurations to the assembly configurations. In doing this, I need to display the "Description" of the component configuration, as opposed to the configuration name or the part number. I know the design table code for the component configuration is...

$CONFIGURATION@"Part Number"<instance>

but what is the code for calling up the description of that part configuration? Can this even be done?

Scott McFadden Aug 20, 2010 11:11 AM

Correct Answer

Ok, I have a question.

You say you can't use a BOM because it would be too large. Understand that.

BUT, if you could use a BOM would you?

I say this because in case you didn't know this, you can split BOM's into several sections.

Maybe your BOM could stretch over a few sheets.

Have you thought about that?

Another method is if you select these components in your drawing you can link a note to the custom property

Then if you can RC on the annotation note and select "Edit Text in Window you can see the code.

Then you may have to add @xxx.sldprt after the description.

Then maybe once you get the code right copy that into your design table.

Maybe this will get down the path you are looking to go.

See the reply in context

No one else had this question

Outcomes

Tomasz Wroblewski Aug 20, 2010 9:36 AM

I use in table Column type ( Custom Property) and property name (Configuration Name)

And I write Description, in Table configuration

Actions

Brent Van Camp @ Tomasz Wroblewski on Aug 20, 2010 9:47 AM

I'm not sure if I'm following your answer, but what I think you're saying to do is use the code $DESCRIPTION. The issue with this is that it will give me the description of the assembly configuration, NOT the sub-component configuration's description, which is what I'm looking for. I honestly don't think I can do what I want, but I'm hoping someone here will know how.

Actions

Scott McFadden Aug 20, 2010 9:48 AM

Brent,

If you can make your BOM parts only and have the column header ( Double click on on the header) point to the custom property Description.

It should show what you are looking for.

Actions

Brent Van Camp @ Scott McFadden on Aug 20, 2010 10:03 AM

I'm not doing this in a BOM, I'm doing it in a design table. I can't use a true BOM because it'd be too big. I have about 20 different assembly configurations, so the BOM get's huge when you display them all. So, what I'm doing is showing a generic BOM with all the components and then using a design table to show the relationship of the few components that have their own configurations. I'll attempt to get a picture of what I'm doing up here so you all can see.

Actions

Brent Van Camp Aug 20, 2010 10:32 AM

Here's a quick explaination of what I'm attempting. I have the following Assembly...

Assembly (with multiple configuraitons)

Part 1 (with multiple configurations)

Part 2 (with multiple configurations)

Part 3 (no configurations)

Part 4 (no configurations)

Part 5 (no configurations)

I can't use a BOM because it will be too large and won't fit on the page since I have too many assembly configurations and too many configurations of parts 1 and 2.

So, I'm using a generic BOM that looks exactly like the above. Then in my design table, I'm showing the connection between the configurations of the assembly and the configurations of Parts 1 and 2. This table ends up being much smaller and more manageable than the BOM would be. I'm using the "configuration name" property in the design table for Parts 1 and 2 to define which configuations are used in the assembly, but I also want to have a column in the design table to display the "configuration description" of Parts 1 and 2. The column header "$DESCRIPTION" will give me the description of the Assembly configurations, but not that of the Part configuration.

Actions

Scott McFadden @ Brent Van Camp on Aug 20, 2010 11:11 AM

Ok, I have a question.

You say you can't use a BOM because it would be too large. Understand that.

BUT, if you could use a BOM would you?

I say this because in case you didn't know this, you can split BOM's into several sections.

Maybe your BOM could stretch over a few sheets.

Have you thought about that?

Another method is if you select these components in your drawing you can link a note to the custom property

Then if you can RC on the annotation note and select "Edit Text in Window you can see the code.

Then you may have to add @xxx.sldprt after the description.

Then maybe once you get the code right copy that into your design table.

Maybe this will get down the path you are looking to go.

Actions

Brent Van Camp @ Scott McFadden on Aug 20, 2010 11:17 AM

Actually, I was unaware of splitting BOMs. Fortunately, I was able to figure a way to use the full BOM on one sheet without having to split it (this time), but I do this kind of thing alot so I'm sure there will be occassion for me to split BOMs in the future. What I was attempting to do was way over complicated and unecessary, now that I know I can split BOMs in the future. Thank you for your help on this.

Actions

Scott McFadden @ Brent Van Camp on Aug 20, 2010 11:20 AM

No problem, I am glad you found resolution to your issue.

Actions

Tomasz Wroblewski @ Brent Van Camp on Aug 20, 2010 11:29 AM

Mayby this help You

1.Config BOM Typ - Top Level

2. BOM Typ - Parts Only

3. BOM Typ - Indented

In this case I create Assembly from Assembly

I suppose that current configuration of the assembly is root, I use Boom Typ (Indented) - that I have name of the assembly and name of the part configuration.

Second name of the column change SW-FileName, and next column change SW-ConfigurationName (Custom Property)

Is this what you want ?

Actions

9 Replies

Tomasz Wroblewski Aug 20, 2010 9:36 AM
Mark Correct
Correct Answer
I use in table Column type ( Custom Property) and property name (Configuration Name)
And I write Description, in Table configuration
Like • Show 0 Likes0
Actions
- Brent Van Camp @ Tomasz Wroblewski on Aug 20, 2010 9:47 AM
  Mark Correct
  Correct Answer
  I'm not sure if I'm following your answer, but what I think you're saying to do is use the code $DESCRIPTION. The issue with this is that it will give me the description of the assembly configuration, NOT the sub-component configuration's description, which is what I'm looking for. I honestly don't think I can do what I want, but I'm hoping someone here will know how.
  Like • Show 0 Likes0
  Actions
Scott McFadden Aug 20, 2010 9:48 AM
Mark Correct
Correct Answer
Brent,
If you can make your BOM parts only and have the column header ( Double click on on the header) point to the custom property Description.
It should show what you are looking for.
Like • Show 0 Likes0
Actions
- Brent Van Camp @ Scott McFadden on Aug 20, 2010 10:03 AM
  Mark Correct
  Correct Answer
  I'm not doing this in a BOM, I'm doing it in a design table. I can't use a true BOM because it'd be too big. I have about 20 different assembly configurations, so the BOM get's huge when you display them all. So, what I'm doing is showing a generic BOM with all the components and then using a design table to show the relationship of the few components that have their own configurations. I'll attempt to get a picture of what I'm doing up here so you all can see.
  Like • Show 0 Likes0
  Actions
Brent Van Camp Aug 20, 2010 10:32 AM
Mark Correct
Correct Answer
Here's a quick explaination of what I'm attempting. I have the following Assembly...

Assembly (with multiple configuraitons)
     Part 1 (with multiple configurations)
     Part 2 (with multiple configurations)
     Part 3 (no configurations)
     Part 4 (no configurations)
     Part 5 (no configurations)

I can't use a BOM because it will be too large and won't fit on the page since I have too many assembly configurations and too many configurations of parts 1 and 2.

So, I'm using a generic BOM that looks exactly like the above. Then in my design table, I'm showing the connection between the configurations of the assembly and the configurations of Parts 1 and 2. This table ends up being much smaller and more manageable than the BOM would be. I'm using the "configuration name" property in the design table for Parts 1 and 2 to define which configuations are used in the assembly, but I also want to have a column in the design table to display the "configuration description" of Parts 1 and 2. The column header "$DESCRIPTION" will give me the description of the Assembly configurations, but not that of the Part configuration.
Like • Show 0 Likes0
Actions
- Scott McFadden @ Brent Van Camp on Aug 20, 2010 11:11 AM
  Unmark Correct
  Correct Answer
  Ok, I have a question.
  
  You say you can't use a BOM because it would be too large. Understand that.
  BUT, if you could use a BOM would you?
  
  I say this because in case you didn't know this, you can split BOM's into several sections.
  Maybe your BOM could stretch over a few sheets.
  
  Have you thought about that?
  
  Another method is if you select these components in your drawing you can link a note to the custom property
  
  Then if you can RC on the annotation note and select "Edit Text in Window you can see the code.
  
  Then you may have to add @xxx.sldprt after the description.
  
  Then maybe once you get the code right copy that into your design table.
  
  Maybe this will get down the path you are looking to go.
  Like • Show 0 Likes0
  Actions
  - Brent Van Camp @ Scott McFadden on Aug 20, 2010 11:17 AM
    Mark Correct
    Correct Answer
    Actually, I was unaware of splitting BOMs. Fortunately, I was able to figure a way to use the full BOM on one sheet without having to split it (this time), but I do this kind of thing alot so I'm sure there will be occassion for me to split BOMs in the future. What I was attempting to do was way over complicated and unecessary, now that I know I can split BOMs in the future. Thank you for your help on this.
    Like • Show 0 Likes0
    Actions
    - Scott McFadden @ Brent Van Camp on Aug 20, 2010 11:20 AM
      Mark Correct
      Correct Answer
      No problem, I am glad you found resolution to your issue.
      Like • Show 0 Likes0
      Actions
- Tomasz Wroblewski @ Brent Van Camp on Aug 20, 2010 11:29 AM
  Mark Correct
  Correct Answer
  Mayby this help You
  
  1.Config BOM Typ - Top Level
  
  2. BOM Typ - Parts Only
  
  3. BOM Typ - Indented
  
  In this case I create Assembly from Assembly
  I suppose that current configuration of the assembly is root, I use Boom Typ (Indented) - that I have name of the assembly and name of the part configuration.
  Second name of the column change SW-FileName, and next column change SW-ConfigurationName (Custom Property)
  Is this what you want ?
  Like • Show 0 Likes0
  Actions

Using Configuration Description in Assembly Design Table

Outcomes

Related Content

Recommended Content