I don’t think this is really possible because ‘schema’. My understanding, and I’m happy to be proven wrong, is that generally when using a database like Coda, you want to keep all of the ‘type data’ on the row, not the column. So you’d be better served by
Monthly Sales Units, instead of [Item A] [Item B] [Item C]`:
[Item], A, 13
[Item], A, 17
[Item], A 11
[Item], B, 110
[Item], B, 80
[Item], B, 33
[Item], C, etc..
This way you can do a lot more with the data, like your averages. Its also how the formulas and buttons ‘think’ - if you want to
AddRows() // add more data // its going to come in the form of a new row.
While it seems like it may be ‘more concise’ to do it the way you have, I’ve found as I’ve migrated from spreadsheets where I would use your current syntax frequently, setting it up as a table with more entries provides way more power.
Another benefit, if you want to add another datum to to
Item A = 13, how do you do it? You can’t right now. But if you had the table, you could add another column
Weight and then give everything another attribute.
Best of luck!