I am putting together a monthly report that will show, over the course of a month, effluent turbidity and chlorine residual values every 15 minutes. I have my data sources set up and aliased but am not getting anything back on the daily version of it that I made for myself as a test. I am getting data returned in the script on the right side of the screenshot here:
Show us your report design, you probably have something wrong with your table data key.
There are likely several problems at once.
The repeating data typically stems from an incorrect data key alias in the table column, when compared to the key browser. Typically when you have a Tag History Data source, the resulting data is all in a single source and the keys are: t_stamp, tag1, tag2 etc.
It seems you have 3 different Data Keys, do you know why that is happening?
I would expect all of the columns to be in tag_history so your table should look like:
t_stamp, Turb, CI2
Notice in your table you have Turb.Turb. That is why you have repeating values. Tables generally work with a single data source, unless you are doing more complex nesting. The table is accessing the very first row of the other 2 data sources every time, because it is only indexing against the "tag_history" data source.
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
But by far and away the best/easiest solution would be to "fix" your data to be a single dataset.
