Reading custom properties from lightweight components in an assembly

Discussion created by Travis Lankheet on Sep 11, 2020
Latest reply on Sep 14, 2020 by Travis Lankheet

Like • Show 1 Like1
Comment • 3

I'm trying to read custom properties from the components in an assembly when that assembly is not Resolved (Lightweight or Large Design). I found this question in the forums that has come to the same conclusion that I have which is the components need to be resolved or the code needs to do an IO file read with document manager:

Custom Property from lightweight component vb.net

I guess my additional question that I want to raise for discussion is, why does the bill of materials have access to these custom properties for the components when an assembly is in lightweight mode but the API doesn't? Is the BOM table using document manger as well or is there some SolidWorks functionality that isn't exposed through the API?

If anyone has any additional insight on this, it would be appreciated.

Outcomes

Wayne Matus Sep 11, 2020 4:05 PM

As a test, make a change to a custom property in one of the parts that is used in the assembly. Save the part file. Open the assembly in lightweight mode and look at the BOM. Does it have the new value for changed custom property? If it is the old value, then that data is just stored as static data in the assembly file.

Actions

Travis Lankheet @ Wayne Matus on Sep 14, 2020 3:26 PM

The table and values must be statically stored once created because the value is the old one when I follow your steps. I also believe it's using Document Manager or some functionality not exposed in the API because when adding a new BOM table in lightweight, it brings in the correct values without resolving the components in the Assembly. Thanks for your help!

Actions

Peter Brinkhuis Sep 14, 2020 3:08 PM

You are right, you have to resolve the assembly component before you can read custom properties from it.

I cannot answer your second question, but of course SolidWorks has more functionality than they expose via the API. You can do certain things in the UI that you cannot do via the API. I guess they build for themselves first, then decide whether to expose it via the API as well.

Actions

3 Replies

Wayne Matus Sep 11, 2020 4:05 PM
As a test, make a change to a custom property in one of the parts that is used in the assembly. Save the part file. Open the assembly in lightweight mode and look at the BOM. Does it have the new value for changed custom property? If it is the old value, then that data is just stored as static data in the assembly file.
Like • Show 3 Likes3
Actions
- Travis Lankheet @ Wayne Matus on Sep 14, 2020 3:26 PM
  The table and values must be statically stored once created because the value is the old one when I follow your steps. I also believe it's using Document Manager or some functionality not exposed in the API because when adding a new BOM table in lightweight, it brings in the correct values without resolving the components in the Assembly. Thanks for your help!
  Like • Show 1 Like1
  Actions
Peter Brinkhuis Sep 14, 2020 3:08 PM
You are right, you have to resolve the assembly component before you can read custom properties from it.

I cannot answer your second question, but of course SolidWorks has more functionality than they expose via the API. You can do certain things in the UI that you cannot do via the API. I guess they build for themselves first, then decide whether to expose it via the API as well.
Like • Show 2 Likes2
Actions

Reading custom properties from lightweight components in an assembly

Outcomes

Related Content

Recommended Content