Find and Replace updating block mtext in modelspace but not within block

[alexWY433]

Strange issue here that I've been puzzling about this morning, hoping I can find some help here. Was hoping to run the find and replace command to change the listed sizing of our structural elements in a drawing. The command correctly finds and replaces all instances of the dimensions (changing 192cm 194cm in this case) for every instance of the text with the exception of mtext objects within blocks. These mtext objects update in modelspace only, while retaining the initial value of the mtext within the block. Exploding the block keeps the replaced mtext shown in modelspace. I've included an example file reproducing the issue. Is there a potential solution for this?

[user181]

make sure you have the option Search Blocks checked in the find and replace dialog box

[alexWY433]

Thank you for your reply. Search blocks is in fact checked.

After running the command, autocad confirms that the string instances were found and replaced, which does reflect in modelspace.

However shown here is the block (selected) which has an mtext value in modelspace of "194cm U" and a value in the block editor of "192cm U". This is not an attribute and I'm not even sure how this is possible. I'm running Autocad 2021  R.47.0.0 if this is relevant. Thank you for your help

[pendean]

... or replace the nested block first, then the top block perhaps? You know, like you really wish to do.

HTH

[alexWY433]

Appreciate your suggestion, but the block contains only an mtext object with a point position parameter. there are no nested blocks within the "000" (excuse my poor naming for this example file) block in the screenshot above. While we could create a new block, reset all block dynamic parameters and run blockreplace, it would be immensely more helpful to find and replace all text within our blocks to the appropriate size. For context, this process is being used to replace the text denoting the width within several slightly different structural component blocks of the same width.

That the find and replace command changes the text in modelspace but not within the block is incredibly strange to me. Under all circumstances I would not think this to be possible that a block could contain non dynamic objects that do not reflect exactly what is in the block.

[nrz13]

I can confirm this behavior in AutoCAD 2022.1.  It is strange and I could see the potential for it to cause construction & liability problems if the blocks are edited in the future because it would change your dimension from what it showed.

Knowing that this problem exists, though, can you work around it by updating the text within the block, which will fix all instances of it, and then do find and replace in the rest of the drawing if needed?

[alexWY433]

Yes, that so far has been the appropriate solution it seems, though of course more time consuming. I am hoping there is a potential resolution to this, as this would help my office immensely; other employees could simply run find and replace to revise all references to the specified dimension in our cutsheets, quantity lists, etc without regard for how this could break block consistency.

For that matter, is this not a bug? Clearly Autocad has no issues finding, and replacing the text within the mtext object with its multiple text styles (what I initially suspected is the problem), but somehow is not replacing text strings within the block itself. I'm a bit busy in the office at the moment but will update if I can find any solution or further issues

[nrz13]

It certainly seems like a bug to me. Unfortunately, none of us here on these forums has the ability to fix it (we're end users just like you).

If you are on subscription, you should open a case through your Autodesk Account to report the issue to Autodesk.  You can share a link to this forum page for their reference as well.  It's possible, although unlikely, that Autodesk could still issue a patch for AutoCAD 2022.  But, if it's at all like it has been in the past, you may not see a fix until AutoCAD 2025 or so.

[alexWY433]

Frankly I have zero faith in Autodesk deigning to fix a little encountered bug when there are still massive issues with the program that have been extant for over a decade and their focus now is exclusively on devising new predatory payment options. Again, appreciate your help. I was hoping maybe someone else had maybe encountered this and knew of some solution. I'll leave this open in case anyone does stumble upon this and can offer their advice. Thank you!