# Reporting Problems

**URL:** <https://forum.inductiveautomation.com/t/reporting-problems/105075>\
**Category:** Ignition\
**Tags:** reporting\
**Created:** [April 14, 2025, 6:39pm UTC](https://forum.inductiveautomation.com/t/reporting-problems/105075 "2025-04-14T18:39:23Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 21, 2025, 5:44pm UTC](https://forum.inductiveautomation.com/t/reporting-problems/105075/6 "2025-04-21T17:44:09Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/c/4cd64db8094dd7a37190acd2d8f820aac22d3462.png)

This part is the "root" of the problem.

Your table is defined to use the `tag_history` data key. So the `t_stamp` row is automatically incrementing through each row. But `Turb` and `Cl2` are being brought in as independent data keys - they're not part of the table. So the reporting module always gives you the first row.

Technically, it's possible to work around this without changing your data, using the builtin Row key and subscripting to pull the correct row out of the additional datasources, as I described here: [Reporting on a single table form different queries - #2 by PGriffith](https://forum.inductiveautomation.com/t/reporting-on-a-single-table-form-different-queries/14491/2)

But by far and away the best/easiest solution would be to "fix" your data to be a single dataset.

---

_[View the full topic](https://forum.inductiveautomation.com/t/reporting-problems/105075)._