Table Value Formatting in Dynamic tables

[pturmel]

You have to dynamically generate the .columns property when you dynamically generate .data. Specify the render property to date where appropriate. You would generally use a custom property to take the dataset format, so you can discover the column types. (Lost if you use JSON return format.)

FWIW, I would use my Integration Toolkit to make expression bindings. Some inspiration here, perhaps:

Automation Professionals' Integration Toolkit Module

I have spent my holiday poking at this. Wanted to provide an efficient replacement for a common use of python transforms: Make a (Perspective) table that dynamically populates both .data and .columns from source dataset that isn't constrained to any particular structure or data types. In Vision, one can achieve this (mostly) by pre-populating the column attributes dataset with all of the possible column names your application might deliver. No such thing in Perspective. But a transform can …