I've been using Draftsight for around 3 years now and when I first started I'd intended to try and make use of the BlockAttributeOutput command that I had seen demonstrated in one of the tutorial YouTube videos, however I could never get the command to work.  I'd assumed that this command had simply been broken during development and would be fixed in a future release.

Having installed Draftsight 2017 SP2 I thought I would give it another try but as before I received the message "No valid entities selected" when issuing the command and selecting my attribute containing blocks.  After tracking down the original Lyons tutorial video I noticed positive comments from only a year ago so I took a second look.  This time I followed the tutorial exactly and found to my surprise that the command worked!

I started trying to determine why my blocks didn't seem to work with this command and came to a possibly surprising conclusion.  I found that if a block was created with attributes that were all set to constant then the command would NOT work on the block.  However, if any of the attributes was altered to not be constant (even if the default value was accepted when inserting the block) then the command would work correctly.  The same goes for the ExtractBlockAttribute command when provided a suitable template file.

Is this a known/intended feature of these commands or an unresolved issue?