Block Property Table - Populate Range Of Cells

[Jason.Piercey]

I've gathered that Excel-like behavior is sorely missing from populating a block property table. You can delete the content from a range of cells but not add content in the same manner. Nor can you copy a range of cells and paste the contents into a new range of the same size. Meh.

Is there any work-around here?

[Jason.Piercey]

I may have spoken too soon here. I seem to be able to copy/paste a range of cells this morning. Not sure what I was experiencing yesterday. I'll have to pay closer attention. Non-issue for now.

[Libbya]

Yeah, copy/paste works fine in block properties tables.  It does not work for multiple cells of a lookup table, though.  

[Jason.Piercey]

Any thoughts on why a user parameter in a block table would be read-only in one block but not another? Both block tables have "Block properties must match a row in the table" checked. In one block the user parameter ends up being a drop-down list in the properties palette but in the other it's greyed out.  I'm guessing you'll want me to post the block but I'd rather not at this time (maybe I can post a simplified version later).

[Libbya]

Your guess is right, and I don't really like guessing.  Off the top of my head, though...  Maybe the user parameter is not in a position on the table where it is fully controlled by other parameters to the left and so it is not editable.   

[Jason.Piercey]

This user parameter is in the last position in both tables and has an order position of 1 in the parameters manager. Both blocks are VERY similar, I'll fiddle with it some more before posting a simplified version.

[Libbya]

Ok, I checked...  If a parameter is on a block properties table and "must match row" is checked, then they will be greyed out if that property lists the same value for more than one row.  Makes perfect sense when you think about it as it would not be possible for cad to resolve what row to select if the user selected a value that was the same for more than one row.  Doing so would create an error so the situation is avoided by making that parameter value read only in properties.

[Jason.Piercey]

I don't think that user parameter has any duplicate values listed but it must... I'll run through all gazillion of them and double check.

[Jason.Piercey]

Yep. Sure enough.  I copied/pasted that column from the block table into excel then instructed excel to find duplicates.  Corrected those values in the block table and it is no longer read only.

Cheers!

[Jason.Piercey]

I've got another one that isn't playing nice with read-only a property. I've verified there are no duplicate values via excel just like I did last time in another block. Back to the drawing board... 

I guess I've got this backwards. I want them to be read-only but this particular data set (one property column) does not have any duplicate values. So, I guess that means I have to use a dummy duplicate value to get the desired behavior. Meh.