# Custom duration in Device Datasets of time series query kind

**URL:** <https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498>\
**Category:** Help\
**Tags:** devices, time-series\
**Created:** [April 28, 2022, 4:36pm UTC](https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498 "2022-04-28T16:36:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gabriella\_Hagedorn\_X](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@Gabriella\_Hagedorn\_X](https://forums.losant.com/u/Gabriella_Hagedorn_X)\
**Post date:** [April 28, 2022, 4:36pm UTC](https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498/1 "2022-04-28T16:36:32Z")

</div>

Hello!

I would like to know if it is possible to create a chart that displays data between fixed date values such as from 03/22/22 to 04/22/22.

The datasets that the platform allows us to select have fixed durations and resolutions. As shown in the figure below:

 ![d52362a755ada376c6c2c612c2057428eb004a48](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/d/d52362a755ada376c6c2c612c2057428eb004a48.png)

For my application, I need the data not to have any kind of aggregation (because I receive it every hour) and a duration of at least 31 days. I know that a possible way to solve my problem would be to use the “Data: Time Series” block, but I believe it would consume extra payloads each time the client requested to see this data. As shown in the following image:

 ![e2e6bb4a01aa9856556dde3fba4513f5de144cd1](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/e/e2e6bb4a01aa9856556dde3fba4513f5de144cd1.png)

So, I was wondering, what would be the best way to do this? I appreciate any ideas.

Thank you!

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [April 28, 2022, 5:54pm UTC](https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498/2 "2022-04-28T17:54:23Z")

</div>

As you’ve correctly noticed, Losant’s dashboards are designed to show a rolling window of the most recent data. It is not currently possible to explicitly pick a window of time to display for individual dashboard blocks.

You can kind of do this by changing the [Dashboard Time](https://docs.losant.com/dashboards/overview/#viewing-past-dashboard-states). For example, if the Time Series Graph was configured for “30 days” and you changed the time of the dashboard to April 22nd, you would see 30 days of data ending April 22nd, which is approximately 3/22 to 4/22.

---

<div class="post-metadata">

**Author:** ![Gabriella\_Hagedorn\_X](https://avatars.discourse-cdn.com/v4/letter/g/d78d45/32.png) [@Gabriella\_Hagedorn\_X](https://forums.losant.com/u/Gabriella_Hagedorn_X)\
**Post date:** [April 29, 2022, 2:10am UTC](https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498/3 "2022-04-29T02:10:57Z")

</div>

Thanks for the answer, Brandon!

Could you tell me if there will be any future updates correcting this limitation?

---

<div class="post-metadata">

**Author:** ![Brandon\_Cannaday](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/brandon_cannaday/32/14_2.png) [@Brandon\_Cannaday](https://forums.losant.com/u/Brandon_Cannaday)\
**Post date:** [April 29, 2022, 3:23pm UTC](https://forums.losant.com/t/custom-duration-in-device-datasets-of-time-series-query-kind/4498/4 "2022-04-29T15:23:25Z")

</div>

It’s a pretty big behavior change to how our dashboards currently work, so it isn’t currently the roadmap.

In terms of using the Data: Time Series Node, only one payload will be consumed for the Endpoint request. In most production applications, endpoint requests generate a fairly small number of payloads when compared to things like device state. Especially when you’ve got thousands of devices all reporting on intervals.
