Attribute disappears when I unlock position

[Steve_Corner]

I have created the attached block which has a few appearance options and some attributes. After creating the block I inserted it in to a drawing and all was good. The attributes were visible in the "Motorised" option. I then decided I needed to be able to move the text so I unlocked the actuator tag attribute. I went back in to the drawing and used attsync to update them and the actuator tag attribute has disappeared. 

I've googled and searched the forum and I can't find an answer. Any ideas?

[Libbya · Accepted solution]

No surprise there.  Attributes need to have their property 'lock position' set to 'Yes' in order to work with dynamic parameters/actions.  Set the attribute back to locked.  If you want to be able to move it around without moving the rest of the block, then add a point/move to the attribute (but keep it locked).

[Steve_Corner]

Thats fixed it. Thanks

[cameronPM92S]

This is not strictly true. I have just now made a block from scratch with a new attribute definition set to lockposition>no, and I can edit the attribute and move it around freely.

HOWEVER

If at any point in time that same block has ANY attribute set to lockposition>yes, then all attributes will become invisible unless they are set to "constant". The handles of the attributes will be visible, even on visibility states that they are not set to be visible on, but the attributes themselves will not be visible and are not able to be edited.

This HAS to be a bug that can be fixed, there's no way that this is working as intended. Does anybody know of the proper channels to report this behaviour to Autodesk?

[Libbya]

Good luck with that.  If you set Lock position to No in a dynamic block, the attribute will not respect dynamic actions including visibility states. Only problems will result.  Lock position = No is also unnecessary within dynamic blocks as you can add any number of point/moves to the block and allow movement of the attribute(s) with Lock position = Yes.

I'm not sure what you are referring to as a bug.  All attributes in dynamic blocks should have their Locked property set to Yes.  If Lock position isn't set to Yes in a dynamic block and undesired behavior results, that isn't a bug, that is operator error for not setting the Lock position property to Yes for attributes within dynamic blocks.

[cameronPM92S]

Apologies, I missed the reference to "dynamic blocks". I should have checked OP's example .dwg he posted.