Stop ATTSYNC reverting existing format and property changes to default

[OTMortimer]

Anyone know how to stop this from happening?

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/AutoCAD-Synchroniz...

Thank you in advance.

[h_s_walker]

If you had read the bit below 

"Solution

This is as designed. The only solution is to plan ahead and not modify attribute tags after numerous instances have been placed in the drawing."

You can't stop it. You have to make sure you have all your attributes in their and sorted first.

[OTMortimer]

Thank you, I had read the original post. However, it's difficult to achieve when your client changes their mind or wants to add some new information onto the plan. I'd like to hear if anyone has found a workaround or solution to the problem that fits my needs.

[h_s_walker]

Have you tried putting the block in a blank drawing making the changes and then using DesignCenter (ADC at the command line) to redefine the block  in the other drawing and see if the changes stay?

[OTMortimer]

I have, unfortunatley this doesn't work

[Libbya]

Using ATTSYNC to advantage is often possible but you have not given enough information on what the actual issue is.  Often the solution is as simple as doing a SAVEAS for the block and modifying the new version rather than the old one in order to avoid using ATTSYNC on the existing insertions, OR using RENAME to change the name of the existing block insertions and inserting the new version of the block for new insertions, OR making sure that any attribute edits do not change the TAG property of the attributes you want to maintain their values, etc....

Post you block, post the file where ATTSYNC is causing issues and give more details.  Asking that AutoCAD not behave as intended is not likely to result in a solution.

[OTMortimer]

Thank you for your reply Libbya. As it happens, I have found a solution that is catered to my specific needs but isn't neccesarily a 'fix all' solution. I've been informed that it's a specific bug relating to dynamic blocks and could be solved using a reactor driven applciation, something that is now (having found a solution for my own needs) beyond my requirements but could be explored in furture. Thank you all the same.