@reithinger wrote:
Hi ActivistInvestor, do you mean, something in my example is wrong or somthing in ACAD is wrong ?
The problem is your block definition. The fields in the table could not have been created via the UI, but appear to have been created by pasting the field expression, e.g.:
%<\AcObjProp Object(%<\_ObjId 2159733957328>%).Parameter(101).UserVariable>%
The ObjectId is the id of the block reference inserted into model space, which isn't valid. If you try to insert a field into the block's definition (in MTEXT or TEXT), you'll see that in the case of anything except for attribute definitions, the BlockPlaceHolder is not available. But what you've created is a field that references an insertion of the block in model space, which is not valid, and is the reason why you are having the issue with object references in your field expressions becoming invalid.
In the drawing you posted, if you copy one of the block references, and then try editing it, the displayed field values are not calculated from to the block insertion you're editing (the copy), because the block's definition contains references to the original block insertion that you copied, rather than the copy of that which you are editing.
You could use attribute definitions and attributes to display data derived from the owning block reference, that can vary with each insertion of the block, but you can't have a text field contained in a block's definition that displays different values that are based on the containing block reference's properties.