tableArray() vs table()

EvanReese

I'm working on a feature that produces a table, but would like subsequent instances of that feature to add additional tables instead of overwriting the last one. Cutlist has the behavior I want. I see that it uses tableArray() and creates multiples in one go by iterating over the composite bodies made by the Cutlist feature and getting the table from each which was stored as an attribute by Cutlist. That defineTable() returns a TableArray, but I'm getting the error that "Return value should be Table, was TableArray" even though the documentation says it should be able to return either. Any ideas or examples I can look at?

Caden_Armstrong

I'm looking for a public sample (I have some private ones I can share directly with you) for the forum knowledge base…

But have you defined the correct return type?

export const bendTable = defineTable(function(context is Context, definition is map) returns TableArray

if you copy pasted a single table feature that has "returns Table", that might be your problem.

Caden_Armstrong

I'm looking for a public sample (I have some private ones I can share directly with you) for the forum knowledge base…

But have you defined the correct return type?

export const bendTable = defineTable(function(context is Context, definition is map) returns TableArray

if you copy pasted a single table feature that has "returns Table", that might be your problem.

EvanReese

That was 100% it, thanks Caden! If I hadn't been trying to do it with my last brain fumes of the day I suppose I could have realized that's exactly what the error message is telling me 🤦‍♂️