# Pass custom Data Key to Chart Component in Report Module

**URL:** <https://forum.inductiveautomation.com/t/pass-custom-data-key-to-chart-component-in-report-module/113316>\
**Category:** Ignition\
**Created:** [January 15, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/pass-custom-data-key-to-chart-component-in-report-module/113316 "2026-01-15T14:59:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [January 15, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/pass-custom-data-key-to-chart-component-in-report-module/113316/1 "2026-01-15T14:59:23Z")

</div>

I want to create a report that displays a dynamic number of sensor data trends. For each sensor on the report page, I need to generate a separate trend chart. Since the number of sensors is dynamic and retrieved from the database, I decided to use a Table Component with an unstructured row, allowing each row to automatically generate a Chart Component for each sensor.

My challenge is how to pass a custom Data Key to each Chart Component. I tried using the Edit Script option under the Property Inspector, but it appears that I cannot change the dataset of the JFreeChart object through the chart script. Additionally, a dataset cannot contain another dataset as a column, so I cannot embed datasets inside a parent dataset.

Given these limitations, I’m unsure how to correctly implement this report design. What is the recommended approach to achieve dynamic per-row charts in this scenario?

 ![Untitled](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/d/6d735703fbce270edb69553b644a4ae2568834b2.jpeg)

---

<div class="post-metadata">

**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:** [January 15, 2026, 3:52pm UTC](https://forum.inductiveautomation.com/t/pass-custom-data-key-to-chart-component-in-report-module/113316/2 "2026-01-15T15:52:02Z")

</div>

Use nested queries for the chart data. Then the data key for the chart is the nested query key. (Automatically delivering the nested chart data for the outer row.)

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [January 16, 2026, 4:39am UTC](https://forum.inductiveautomation.com/t/pass-custom-data-key-to-chart-component-in-report-module/113316/3 "2026-01-16T04:39:34Z")

</div>

Oh it seems Report module Key Browser doesn’t show children of nested dataset but components understand and use it. Here `TrendDS` has `t_stamp` and `value` column inside.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/9/69055d4dece787984d2f5c1432e59a4d219ac597.png)