# Reporting Module Table - Use column index instead of column name **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [April 19, 2024, 7:58pm UTC](https://forum.inductiveautomation.com/t/reporting-module-table-use-column-index-instead-of-column-name/89140 "2024-04-19T19:58:14Z")\ **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:** [April 19, 2024, 8:47pm UTC](https://forum.inductiveautomation.com/t/reporting-module-table-use-column-index-instead-of-column-name/89140/2 "2024-04-19T20:47:05Z")
The table in the report will need consistent names. Use a script data source to present the unchanging names it will need. To work with script data sources, you probably want to review this: > [@Report with Scripted Nested Data](https://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801): > > The report datasource scripting examples explain how to access the nested data in another key for use constructing a custom dataset. What I don’t see is how to construct nested data that would be suitable for use with a child table in a table group. I have a parent dataset that I’m constructing via script due to annoying limitations of an ancient SQL Server 2000 instance. I need a subquery for each row that could be done with a normal query, but there’s no way to add a regular subquery to a s… and this: > **[Scripting Data Source | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/reporting/report-data/scripting-data-source#script-data-source)** > > Script Data Source --- _[View the full topic](https://forum.inductiveautomation.com/t/reporting-module-table-use-column-index-instead-of-column-name/89140)._