# Adhoc Trending datapull

**URL:** <https://forum.inductiveautomation.com/t/adhoc-trending-datapull/55575>\
**Category:** Ignition\
**Tags:** vision, ignition81\
**Created:** [January 31, 2022, 10:11pm UTC](https://forum.inductiveautomation.com/t/adhoc-trending-datapull/55575 "2022-01-31T22:11:59Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![josborn](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@josborn](https://forum.inductiveautomation.com/u/josborn)\
**Post date:** [February 1, 2022, 12:03am UTC](https://forum.inductiveautomation.com/t/adhoc-trending-datapull/55575/4 "2022-02-01T00:03:33Z")

</div>

> [@Easy Chart. Export to excel](https://forum.inductiveautomation.com/t/easy-chart-export-to-excel/12738/2):
>
> What is the tag history resolution and resolution mode set to on the easy chart? This will effectively determine the time between the records that are returned from its historical query. If you find that the xls is returning this way regardless of this setting, then a better option will be to make a new button with a script that performs its own tag history query and saves an Excel file, using the system.tag.queryTagHistory() and system.dataset.exportExcel() functions.

Looks like the history resolution is the way to adjust the interval. I did test dataset.exportExcel() with 4 million rows, and it does stop at 1,048,576.

I don't have a tag history with nearly enough rows, but i did manage to create a test table with 4 million rows and plot it with a regular chart, which my cpu very much did not like.

---

_[View the full topic](https://forum.inductiveautomation.com/t/adhoc-trending-datapull/55575)._