Disable or change Instance properties to Custom Properties in BOM

[tuliobarata]

Hi all,

I'm using  Inventor 2023 filling the manual BOM fields inside Assemblies, but I'm having some problems with custom and instance properties.

I don't need to make different properties, so I need that the properties filled in the BOM propagates to all instances of my sub assemblies (keeping a black text).

But sometimes (couldn't understand why), the field keeps Instance property only (blue text).

I've checked the sub assemblies and all are with the correct representation/model state/design view in the assembly. And all of them are with Edit Factory Scope enabled (so any changes would be in the custom properties of all instances).

When I click with right button and try change to CUSTOM, nothing happens. If I delete the values and try again from the BOM view, doesn't change and keeps with blue text.

The only solution I've found untill now is yo enter in each Sub, go to iproperties>Custom, then edit each field writing and space in the end of value, ENTER, delete the space and ENTER again, so the properties are propagated to all instances/states and in the Assembly BOM the text becomes black (considering the edit factory scope option is ON).

How can I change it to custom property and propagate to all instances directly from the Assemblies BOM ?

BOM with some custom and some instances properties:

Edit factory scope enabled for all sub assemblies:

Representation of all subs are ok inside the main assembly (I need to use the FINAL one for now):

Trying to change to CUSTOM:

Thanks!

[johnsonshiue]

Hi! I could be wrong but I don't think this is a good workflow to perform in the BOM table. The issue here is that you have duplicate properties (custom iProperty and instance property). They share the same name and they are listed on a last-come-first-serve basis. This means the instance property can "override" the custom property. I personally would avoid using any duplicate property name. You may end up with very confusing behaviors in the drawing.

Please make property name unique.

Many thanks!

[tuliobarata]

@Hi @johnsonshiue , thanks for your reply.

Understood. 

But here the only reason I use differents instances is because of the Level Of Detail LOD (now, model state), that I need to use in some assemblies when I need to show or suppress some reference. 

I'm using this way because I need e.g. the name of one assembly be exactly the same in all of my LODs, so I keep the "toogle edit scope" option enabled, except when I really need to suppress or show something, otherwise, all the data manually inserted in the Assembly BOMs shall be the same in all model states.

At least nowadays with my templates (I'm using them for some years), I don't need to have different custom properties in the same file.

So if I use the model state 1 or model state 2, I need the same information goes to my IDW, because of that I wanna to fill the BOM and propagate the information to all instances of the file.

Thanks.