Currently, Tables accept an object of arrays only, that maps to how a SQL database would return data. Our REST APIs use, as one would expect, arrays of objects however, and this means that I have to write fairly complex transformations for every API call that needs to be shown in a table.
It would save us hours, and let us use our REST APIs more than database accesses, if tables had support for this notation. I'll provide some simple examples below:
Yes, when I tried yesterday, it wouldn’t add any columns to the table, and I couldn’t manually add any columns to the table until I changed the data source. After changing the data source, lots of custom columns would appear based on how many times I had previously pressed it. Let me try to replicate here later today, and I’ll share.
Strangely, I cannot replicate it today. Now it is working, last night I struggled with it for some time, but the same API calls that resulted in a broken table yesterday, now behave as expected.