Why isn't my width attribute on my dynamic window block reading correctly?

Why isn't my width attribute on my dynamic window block reading correctly?

johnrmcwatersiii
Enthusiast Enthusiast
1,356 Views
10 Replies
Message 1 of 11

Why isn't my width attribute on my dynamic window block reading correctly?

johnrmcwatersiii
Enthusiast
Enthusiast

I created a dynamic block for a standard clad window, and I have a width attribute that is supposed to state the width of the window based on a line that stretches. However, all I can get it do is read '####'. Everything within the block looks okay, and I've tried UPDATEFIELD and ATTSYNC, but to no avail.

 

Any help is much appreciated.

0 Likes
Accepted solutions (1)
1,357 Views
10 Replies
Replies (10)
Message 2 of 11

steven-g
Mentor
Mentor

Can you post a dwg that shows the block with this problem. When I insert your block into a drawing it works just fine.

0 Likes
Message 3 of 11

johnrmcwatersiii
Enthusiast
Enthusiast

@steven-g 

 

Thank you for looking into this.

 

I've attached a dwg that still shows the width as #### for me.

0 Likes
Message 4 of 11

cheryl.buck
Autodesk Support
Autodesk Support

Hi @johnrmcwatersiii,

 

Thank you for the file. It looks like the Field object shows as not valid when I double click the field value, and Unknown in the Field dialog.  Try reselecting the Field object. 

 

Capture.JPG

 

Please let me know if that helps. 

 

Click the Accept Solution button to mark any posts that provide the answer or solution.

Likes are always welcome.

 

All the best,

 

 

Cheryl Buck
Technical Support Specialist



Did a post answer your question or help resolve the issue? Please click the Accept Solution button.
If you find a response helpful, consider Liking the post.

0 Likes
Message 5 of 11

johnrmcwatersiii
Enthusiast
Enthusiast

@cheryl.buck 

 

The definition is referenced to a line within the block. Could that be the reason it's unable to find anything when you double click it?

0 Likes
Message 6 of 11

Libbya
Mentor
Mentor

Object fields are less reliable than BlockPlaceholder fields.  Considering you already have the Window Width parameter which appears to be the value you are trying to display, I would recommend eliminating the object field (and the line it references) and using an BlockPlaceholder field referencing Window Width instead.  

0 Likes
Message 7 of 11

Libbya
Mentor
Mentor
Accepted solution

Edit the attribute name and run an attsync to relink existing block definitions that have lost their link.  See screencast.

 

 

0 Likes
Message 8 of 11

johnrmcwatersiii
Enthusiast
Enthusiast

@Libbya 

 

Thank you for the input. I may try that, but for some of these blocks, the width read out will actually be different from the total width of the block. For instance, if the window as brick moulds on either side. 

 

edit: I see what you're doing now...you can reference the window width as a parameter.

0 Likes
Message 9 of 11

Libbya
Mentor
Mentor

@johnrmcwatersiii wrote:

 

Thank you for the input. I may try that, but for some of these blocks, the width read out will actually be different from the total width of the block. For instance, if the window as brick moulds on either side. 


In that case, the concept is the same.  I think you will find that you get more reliable field results if you add an appropriate parameter instead of a line and use that parameter value as a BlockPlaceholder field rather than an object field referencing a line.  Have0 grips for the referenced parameter if you want it invisible.   

0 Likes
Message 10 of 11

johnrmcwatersiii
Enthusiast
Enthusiast

@Libbya 

 

Thank you for your time and help.

 

Any idea why referencing objects like lines isn't as stable?

0 Likes
Message 11 of 11

Libbya
Mentor
Mentor

I do not know why fields lose their link or why object fields are less reliable than blockplaceholder fields.  Renaming the attribute that contains the field and running ATTSYNC to relink fields should work in either case, though.  

0 Likes