# Report Line Graph Problem

**URL:** <https://forum.inductiveautomation.com/t/report-line-graph-problem/3783>\
**Category:** Ignition\
**Created:** [December 20, 2011, 4:13pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783 "2011-12-20T16:13:23Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlexW](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@AlexW](https://forum.inductiveautomation.com/u/AlexW)\
**Post date:** [December 20, 2011, 4:13pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/1 "2011-12-20T16:13:23Z")

</div>

I believe Dave already created a ticket for this but just wanted to give some background to the request.

I wanted to create a daily production report including daily totals as well as a trend charting shift totals for the past three months. The shift totals are stored once every 12 hours.

I had everything set up correctly however according to support, the line graph in the report module doesn’t support trends where the points are too far apart or where there is no discernable pattern.

Obviously there are lots of applications where the data will only be captured once or twice a day so it would be great if the line graph could support trending this kind of information.

I was surprised that this would be a problem… usually isn’t a line graph supposed to just plot a series of x,y coordinates?

Thanks in advance

Alex

---

<div class="post-metadata">

**Author:** ![AlexW](https://avatars.discourse-cdn.com/v4/letter/a/b5a626/32.png) [@AlexW](https://forum.inductiveautomation.com/u/AlexW)\
**Post date:** [January 3, 2012, 6:20pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/2 "2012-01-03T18:20:06Z")

</div>

Does anyone know if this is something that will be fixed or has a work around for this?

What is the time frame for the fix if there is one?

I guess I could plot it vs index rather than time stamp but it would be nice to know the time frame of the various points

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [January 3, 2012, 7:45pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/3 "2012-01-03T19:45:28Z")

</div>

We’d have to put in a change for the reporting module that used a different kind of line renderer to support non-uniform data.

This can be done for 7.3.4. We don’t have a release date for that (7.3.3 is currently being tested for release), but a beta of it should be available shortly after the 7.3.3 release.

---

<div class="post-metadata">

**Author:** ![DennisWomack](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@DennisWomack](https://forum.inductiveautomation.com/u/DennisWomack)\
**Post date:** [January 3, 2012, 8:57pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/4 "2012-01-03T20:57:41Z")

</div>

…and how close to release is 7.3.3?

I know I shouldn’t ask.

Thanks, Carl.

May 2012 be a very Prosperous New Year for you Ignition developers.

Dennis

---

<div class="post-metadata">

**Author:** ![Dravik](https://avatars.discourse-cdn.com/v4/letter/d/e274bd/32.png) [@Dravik](https://forum.inductiveautomation.com/u/Dravik)\
**Post date:** [January 3, 2012, 10:27pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/5 "2012-01-03T22:27:21Z")

</div>

If they are anything like one of my fav software houses…

“soon™”

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [February 3, 2012, 6:20pm UTC](https://forum.inductiveautomation.com/t/report-line-graph-problem/3783/6 "2012-02-03T18:20:08Z")

</div>

Haha, yes, everything will be here “soon”.

7.3.3 was released. This fix is in for 7.3.4.
