# Change number format for all elements of table **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [February 22, 2025, 12:57am UTC](https://forum.inductiveautomation.com/t/change-number-format-for-all-elements-of-table/102722 "2025-02-22T00:57:59Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [February 22, 2025, 2:13am UTC](https://forum.inductiveautomation.com/t/change-number-format-for-all-elements-of-table/102722/4 "2025-02-22T02:13:45Z")
If you are starting with a convential dataset (NQ or historian), it is best to bring that binding to a view custom property, keeping dataset format. Then you can bind `props.data` to convert the data to JSON, and simultaneously bind `props.columns` use the ordered column information (name and data type). Some example code here, even if you don't use my toolkit: > [@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/change-number-format-for-all-elements-of-table/102722)._