Complex Dynamic Block Issues

[mbrandt5]

I have a fairly large dynamic block that is fairly sporadic.

When I attsync it, some fields within attributes lose there values, lookup strings, or object measurements. while others update...

Not as many lose there values with the sync button in battman command

This dynamic block contains up words of 500 parameters.

Also, approximately 20 plus lookup tables

No constraints are used...

Is this a common occurrence with complex dynamic blocks?

I'd prefer not to post the block since I've spent weeks to months working on it, but may if its absolutely nessecary

[mbrandt5]

and 24 attributes

[mbrandt5]

Also when I switch between visibility states I also lose the value of an field value in an attribute

[LSElite]

I have made block of a similar size and never had a problem.
you seem to be having a lot of problems with attsync.
If you want to attach the block I can check to see if it works on my version of cad?
It may be a bug in your version.
I used to experience alot of bugs in the block editor is 2012 which I no longer experience in 2015.

[mbrandt5]

I allows have alot of parameters pulling other parameters...I have a version of 2015 in my office as well so ill try that tomorrow thanks go the advice

[steven-g]

Have you noticed any pattern as to when these problems show up, is it possible to recreate the problem in another block with fewer objects?
What sort of things are you altering or updating that need the attsync command in the first place, that might give a clue.
I came across a problem yesterday with attsync when using the block editor to alter an attributes default value, that contained both text and a field. All I changed was the text and it refused to update/change with attsync, until I also changed the tag value as well.

[mbrandt5]

I apologize for my lack of knowledge what do you mean tag value...

Also a thread I came across where people got null values of #### was

http://forums.augi.com/showthread.ph...Dynamic-Blocks

[mbrandt5]

The issue to the best of my knowledge was caused by multiple attributes containing fields of a different attribute value...

It did not make a difference using 2015...so if someone reading this works at autocad...that may be something to look into fixing

[steven-g]

I apologize for my lack of knowledge what do you mean tag value...

Also a thread I came across where people got null values of #### was

http://forums.augi.com/showthread.ph...Dynamic-Blocks

I meant the attribute tag name, in the sitution I mentioned I wanted to change the letter X in the default box and leave the field alone, but it wouldn't update unless I also made a change to the tag name (the fact that they where both X is irrelevant I think), I have no idea why it made a difference, but I thought it was worth mentioning. There is also an issue in dynamic blocks with attributes referencing other attributes in the same block, and that is usually solved by performing a dynamic action on the block it could be that fields can give similar problems.
tag.jpg

[mbrandt5]

the mtext worked out better for user input overall...and maybe that information was in a autocad manual...if not though thought I'd bring it to peoples attention