# Table Value Formatting in Dynamic tables **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [July 28, 2026, 9:12pm UTC](https://forum.inductiveautomation.com/t/table-value-formatting-in-dynamic-tables/116564 "2026-07-28T21:12:06Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 28, 2026, 10:00pm UTC](https://forum.inductiveautomation.com/t/table-value-formatting-in-dynamic-tables/116564/2 "2026-07-28T22:00:46Z")
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](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/5): > > 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 … --- _[View the full topic](https://forum.inductiveautomation.com/t/table-value-formatting-in-dynamic-tables/116564)._