Repeated Block Attributes

Repeated Block Attributes

Anonymous
Not applicable
7,045 Views
29 Replies
Message 1 of 30

Repeated Block Attributes

Anonymous
Not applicable

I have searched the entire AutoCAD LT forum for, what I thought would be, a simple solution.  I have found others asking my same question but it was from over 10 years ago, there was no resolution.  I am hoping there is now a solution in LT. 

 

I am creating terminal blocks and section view lines.  Basically these are symmetrical objects that physically have the same number or letter on each side of them.  I have created dynamic block for these items however I cannot seem to create a block attribute that works for me.  I want to make a single block attribute that basically is used in 2 places.  Or 2 block attributes that are updated by a single input.  So if I put "1" on terminal "1", the number displays on both side of the terminal block.  Similarly with my section view arrows.  Am I just totally missing something obvious or is this not possible?  I have attached my section view callout block.

 

Thanks,

Steve O

0 Likes
Accepted solutions (1)
7,046 Views
29 Replies
Replies (29)
Message 2 of 30

pendean
Community Legend
Community Legend
FIELD command is the only method for which you can duplicate an entry you wish to replicate. Try it out, you ant to start with the OBJECT type in the pop-up.
0 Likes
Message 3 of 30

Anonymous
Not applicable

Thank you Dean, I got it working.  How to I make it update?  It seems like the value in the field just remains the same.

0 Likes
Message 4 of 30

Anonymous
Not applicable

I was looking at this this afternoon and have not managed to get the block to auto-update. I have tried the visibility option but to no effect.

 

See this thread for further insight!

0 Likes
Message 5 of 30

h_s_walker
Mentor
Mentor

You have to do a REGEN. Unfortunately fields do not "auto" update

Howard Walker
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Left Handed and Proud

0 Likes
Message 6 of 30

Anonymous
Not applicable

Ah! That simple....

0 Likes
Message 7 of 30

Anonymous
Not applicable

Field.PNGDyn Block.PNGAtt Def.PNGInserted.PNGFinal.PNG

0 Likes
Message 8 of 30

Anonymous
Not applicable

There was supposed to be text with each one of those pictures I just uploaded.  I added it but it didn't come through.  I am attempting to show that I added the Field to a Dynamic Block while in the Block Editor.  I want the field to be the value within the block attribute called SECTION.  I believe I followed all of the instructions provided above but I cannot get the field to update.  It will only match the Default value of the Block Att.  I have tried REGEN and UPDATEFIELD. Nothing works for me.  Am I missing something?

 

Thanks,

0 Likes
Message 9 of 30

pendean
Community Legend
Community Legend
Post the DWG file with the block in it.
0 Likes
Message 10 of 30

Anonymous
Not applicable

See attached.

0 Likes
Message 11 of 30

pendean
Community Legend
Community Legend
Ah, it's all one single block: FIELD command doesn't work inside the block to update itself, you need two blocks.

Can you use preset digits/letters in your dynamic block? The folks in the dynamic blocks forum might have more ideas to try.
0 Likes
Message 12 of 30

Libbya
Mentor
Mentor
Accepted solution

You can certainly use fields within a single block to repeat an attribute value.  Here's a step-by-step screencast:

Message 13 of 30

pgoing
Contributor
Contributor

Is there any way to have multiple attributes in a block, set with their value = a field that looks up the value of another attribute in the block; but then only list the one look-up attribute in the attribute editor?  Because even with a "Do not edit!" prompt, users edit it. 

0 Likes
Message 14 of 30

Libbya
Mentor
Mentor

Unfortunately, no.  All visible attributes will show up in the 'edit attributes' dialog and there isn't a way to prevent users from editing them that doesn't carry its own set of issues. 

 

One possible solution is to place the attributes you do not want edited onto a locked layer.  Keep the editable attribute on an unlocked layer and place the attribute with the field on a locked layer.  That prevents a user from editing the attribute on the locked layer but there are a few downsides: the user cannot use the double-click to enter the attribute editor and instead they need to edit the attributes in properties, they can always simply unlock the layer and edit the attributes you don't want them to edit, and unfortunately attribute justification no longer works for any attributes that aren't justified to the left.  See screencast.  

 

Education, carrot, and stick are probably your best recourse to getting users to behave appropriately.  I understand your pain.  Maybe keep an automatic sync backup for all file saves and when a field is wiped out, pinpoint the culprit by looking at the backup file versions, and educate them accordingly.  

 

  

 

0 Likes
Message 15 of 30

Anonymous
Not applicable

Thank you so much, using 2 attdef, and then default to be updated by field. genius!

0 Likes
Message 16 of 30

trevor.meissner
Explorer
Explorer

I have followed this video to a T and when I enter a new "parent" value and regen the "child" value doesn't update. Any ideas on why this may be happening?

0 Likes
Message 17 of 30

Libbya
Mentor
Mentor

Best guess is that you missed something.  It would improve (by several orders of magnitude) my ability to guess if you attached your block.  

0 Likes
Message 18 of 30

trevor.meissner
Explorer
Explorer

File attached.

0 Likes
Message 19 of 30

Libbya
Mentor
Mentor

You need to perform a dynamic action in order for fields to begin working within a block.  That dynamic action only needs to be performed once for any insertion.  Fields within copies of a block that have performed a dynamic action will also function.  Insertions performed from a tool palette tool made from a block that has performed a dynamic action will also work immediately without any further dynamic action.  The dynamic action does not even need to change anything.  In the following screencast I add a user parameter to your block.  In modelspace I then edit that user parameter (which counts as a dynamic action) and from that point forward the field works.  

Message 20 of 30

trevor.meissner
Explorer
Explorer

Thank you, thank you, thank you. This is a huge weight lifted. I really appreciate the quick response. Have a good day!

0 Likes