custom property not accessed by bom

I have two instances of a part model in an assy, and each config of the part
has a user specified property (config specific) "Number" that's used in the
bom. The "Number" property shows up fine in the second instance of the
component, but not the first. I've tried changing the "Part Number
Displayed" value to make the two instances display differently but no help
(I think that was necessary in Excel bom's).
Is this a bug in the new table function, or am I missing something?
sw2004sp4.1
Thanks
Bill

 

just found the problem, assembly was referring to default config, instead of
the one I intended.

another problem, though, is that after changing the config of the component,
the component
now appears out of assembly order, should have been 4, but came out as item
7.
I haven't seen that before.

Bill

 

If you click "follow assembly order" in your BOM properties, it will
re-order properly. I always set the option "do not change numbers" (or
something like that) after they have been re-ordered. This prevent them
from "self" re-ordering until you tell it to.

 

that did the trick. i had clicked that before, but nothing happened, so i
gave up on it.
the second time, though, it worked like you said.
i guess i'm being paranoid about sw2004sp4.1
thanks
bill