# Using Timeframe Selector as an input for a DQL query

**URL:** <https://community.dynatrace.com/t/using-timeframe-selector-as-an-input-for-a-dql-query/38758>\
**Category:** Developer Q&A Forum\
**Tags:** strato, coding-assistance\
**Created:** [March 9, 2023, 8:30am UTC](https://community.dynatrace.com/t/using-timeframe-selector-as-an-input-for-a-dql-query/38758 "2023-03-09T08:30:31Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![3ene](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/3ene/32/33646_2.png) [@3ene](https://community.dynatrace.com/u/3ene)\
**Post date:** [March 9, 2023, 9:43am UTC](https://community.dynatrace.com/t/using-timeframe-selector-as-an-input-for-a-dql-query/38758/3 "2023-03-09T09:43:54Z")

</div>

Hi Stefan,

that’s cool, but I now run into a different issue: How do I default set TimeframeDetails to now()?

I’d like to run a query immediately on app start and therefore need to have TimeframeDetails already set to now. Is there a way to translate between Timeframe and TimeframeDetails?

---

_[View the full topic](https://community.dynatrace.com/t/using-timeframe-selector-as-an-input-for-a-dql-query/38758)._
