Redefined blocks not cooperating when added to new tool palettes

[Anonymous]

I have having an EXTREMELY annoying and frustrating experience trying to add redefined blocks to new tool palettes.  These blocks have two attributes, and one of them has to be changed from "X" to an item-specific inventory number...otherwise whenever the block is pulled off the tool palette, the same inventory number (which NEVER EVER changes) has to be re-entered every time into the attribute field.  Yes, it needs to stay an attribute because of how the info gets pulled out of these blocks.

I've tried editing the attribute field after copying and pasting the block onto the palette, but that NEVER works, it's like the palette has some kind of overriding control over the block.

So in the interm, I'm exploding the blocks, changing the "X" value to the inventory number, and redefining the whole block.  When I use the Insert command and re-insert the bock, it comes in just like it should, with the updated inventory number showing right away in the specified attribute field.  HOWEVER...the second I copy and paste the block into a tool palette, then try to drag the block off the palette, it IMMEDIATELY changes the inventory attribute back to "X" and screws up the alignment of that "X" in the block.

WHY on Earth does putting the block onto/dragging it off a palette mess up the block definition??  The original definition was purged out of the dwg enitrely, and an entirely new block definition created with the correct entries.  It inserts fine from the "Block" tab in the ribbon, so why should the palette be messing everthing up??? 

[dbroad]

1. In order to redefine blocks with palettes, it is best if the block placed on the palette be a block within a drawing and not a drawing file itself.

2. In order to redefine blocks with attributes, first use the redefine option on the palettes and then either the attsync or battman command to update the changes to attribute definitions.  Exploding is not necessary.

[rkmcswain]

Where is the definition of the block in your tool palette?
Inside of a .dwg file somewhere, or is the block its own .dwg file somewhere?
It sounds like the TP button may be referencing a copy of the block that isn't what you think it is.

[stevetamplen]

Hello neeboy042274;

What version of AutoCAD are you using?

If you create a new block in a new drawing, does it behave the same way?

Can you please post a drawing with the questionable block in it?

[Anonymous]

I have all the original blocks inside of one drawing file that I am trying to work through this process with.

I just tried the BATTMAN command also; see the attached screenshots...no dice, the minute I copy to the tool palette, and try dragging it off the tool palette, it all goes to hell.  You can see that the ASSY TAG has reverted to X, and the position of that X is off from the original block.  Again, these problems do not appear when inserting from the ribbin, they only keep happening after using the **** tool palettes.

[Anonymous]

I am on ACAD 2016 Mechanical.  I will see about posting a dwg...

[Anonymous · Accepted solution]

***SIGH*** It would appear that once I make the necessary edits to the block, then copy that block to a new file (and keep adding subsequent blocks to that file), the problem completely disappears.  I always tell people that AutoCAD is the most stable program I've ever work with, which is still true, but it's moments like this that REALLY test me.

[stevetamplen]

I am just glad that it is all worked out.

[Anonymous]

Sooo... What IS the answer?

I'm on LT 2018 and having dynamic blocks reverting to a previous version once I hit 'redefine' in the tool palette. I edit the block (add a new visibility & new geometry), then exit the block editor. I test the functions of the block. All is well. Then save the file. So far so good. Then update the block in the tool palette with 'redefine'. Boom, the changes are gone.

I'm not understanding the answer as it is stated... Am I suddenly forgetting a step in the process? If I've been doing it wrong all along, then ...why would it have worked before and suddenly not now??

Thanks

UPDATE:

Still stuck on this one. I also tried bringing the block into a new file, making the changes, changing the block name, and copying that to the original file (source file). But when I add THAT renamed block to the palette, there is a different error where it is listed in the palette but with a big white square instead of a picture of the block. Hmm....

If this were really important to my project, I'd be pulling my hair out right about now. Any suggestions?

[cadffm]

If I understand right:

You have a template.dwg with Blocks,

added one (dynamic) Block"A" to a Toolpalette, this step created a insertion Toolpalette tool (i am not sure for the right english word for this)

You create a blockreference of that Block"A" in another Testfile.dwg, edit the Block"A" in template.dwg&save this file.

Back in Testfile.dwg you are using rightclick->redefine for Block"A" and now.. the old created blockreference of Block"A":

1) Is updated well, has the new feature and perhaps the edited objects/properties.

but

2) The VALUE of one or more dynamic properties are reseted, right?

Answer: You changed something which Acad can not handle.

>> (add a new visibility & new geometry)

That alone is NOT a Problem, I am sure between create the "old" blockreference and your last step "(add a new visibility & new geometry)" there

was more/other changes on this blockdefinition (in Testfile.dwg)

For example: Delete and recreate an parameter.