# Truncating data in Ignition Reporting **URL:** \ **Category:** Ignition\ **Tags:** scripting\ **Created:** [June 19, 2018, 5:55pm UTC](https://forum.inductiveautomation.com/t/truncating-data-in-ignition-reporting/18530 "2018-06-19T17:55:02Z")\ **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:** [June 19, 2018, 6:42pm UTC](https://forum.inductiveautomation.com/t/truncating-data-in-ignition-reporting/18530/2 "2018-06-19T18:42:07Z")
> [@harryzhou4498](#): > > I'm having issues finding out how exactly I can "truncate" data points in Ignition's reporting. It seems like the only values I can really change to control this are startdate and enddate with a timeseries chart? One way or another, you are either going to write SQL that excludes the unwanted data, or you are going to [write a script](https://docs.inductiveautomation.com/display/DOC79/Scripting+Data+Source) that omits the unwanted data from a "raw" historical query. Either way, you end up with a data key for the chart that is already filtered. Since the boundaries are also historical (the button status recordings), I would lean towards a script. You've asked about button intervals before--it seems [that answer](http://forum.inductiveautomation.com/t/trying-to-calculate-the-time-between-two-tag-changes/18246/5) is still valid. --- _[View the full topic](https://forum.inductiveautomation.com/t/truncating-data-in-ignition-reporting/18530)._