Dimension object missing Measurement value in Field menu

atrotto
Enthusiast
Enthusiast

Dimension object missing Measurement value in Field menu

atrotto
Enthusiast
Enthusiast

Very niche thing that has just started happening recently...

 

We have a table in paperspace populated with fields that are linked to dimensions in modelspace, and it has worked in the past, however, occasionally when we try to make a new field, in the field menu there is no "measurement" property listed, even though the object is recognized as a "rotated dimension".

 

This can be fixed by creating a new dimension, but if we can figure out why this happens that would be great.

 

The workspace is currently using both AutoCad2021 and 2024 if that is relevant, however it has happened with files that have exclusively been handled with 2024. 

0 Likes
Reply
623 Views
6 Replies
Replies (6)

TheCADnoob
Mentor
Mentor

Any chance it is related to the dimension style?

 

If you do a MATCHPROP between dimensions that work and vice versa, does it make a difference?

 

If you change the style of the dimensions does it make a difference?

 

Can you share your drawing?

 

 

--

Something you can try that might be an ugly work around would be dropping in the field code strait into the text of the cell. My guess is that this wont work but might be worth a shot. 

 

in your table, insert a field that ready something like the layer. 

in the field dialog copy the filed field expression from the field dialog. 

 

TheCADnoob_0-1714753541685.png

 

 

Take that snippet and remove the last part, everything from the period on. 

 

%<\AcObjProp Object(%<\_ObjId 1919861958752>%).Layer>%

 

make it look like

 

%<\AcObjProp Object(%<\_ObjId 1919861958752>%)

 

Next Add

 

.Measurement \f "%lu2">%

 

It sholud look like this now

 

%<\AcObjProp Object(%<\_ObjId 1919861958752>%).Measurement \f "%lu2">%

 

Now copy that string and paste it into a cell (not a field). It should convert the cell to a field and refer to the measurement property. This may not work as i suspect that since the option isn't showing up in the field it may not be a value that can be referenced but it might be worth checking to see if it can if you are in a pinch. 

 

CADnoob manual field manipulation.gif

CADnoob

EESignature

pendean
Community Legend
Community Legend

@atrotto wrote:

...This can be fixed by creating a new dimension,...


How is a new dimension fixing it exactly? Show us in screenshots or a detailed step-by-step, I suspect you might just be missing a step for a fix instead.

0 Likes

ChicagoLooper
Mentor
Mentor

@atrotto 

Based on the image you uploaded in your opening post, describe the object you select AFTER clicking the green Object Type button?

fieldissue.png

 

After selecting that object, can you upload an image of it? Can you include the Properties Palette in your image so that selected object can be evaluated? 

 

Chicagolooper

EESignature

0 Likes

atrotto
Enthusiast
Enthusiast

After looking at all of your imput, what I thought was going on is definitely happening. 

 

A little context:


These files were handed off from one user to another, and only the dimensions that were existing before the handoff (and copies of these dimensions) had this issue. When I go into the properties menu of the dimensions, there is no value for measurement.

 

A more succinct fix has been figured out, reassociating these dims to the geometry they are on seems to make the value come back. This might also explain what's going on; however, I do not remember having an issue pulling a measurement value from an unassociated dimension before. 

ChicagoLooper
Mentor
Mentor

@atrotto 

A ‘best practice’ is dimension everything, no exceptions.  Do NOT copy an existing dimension and paste it onto another object. Perform the dim operation again, whenever needed. 

 

Copying and pasting a dim is so _________. (Fill in your own adjective.)

 

 

Chicagolooper

EESignature

atrotto
Enthusiast
Enthusiast

Rest assured, the copied dimensions were simply for the sake of troubleshooting. I wanted to see if it was an issue of the dimension object being somehow "not updated" or if the object truly had the measurement value deleted from it. It appears to be the latter. 

0 Likes