If all of the bindings are pulling from your query dataset, consider dynamically generating the entire props.columns list using the dataset's metadata. Some techniques:
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 …
(Whether you use my toolkit or not.)
1 Like