So, your dropdown input gives you a date from any search (let's populate the input with this example to propose today and the previous 14 days): | makeresults count=14 | streamstats count as offset | eval _time=_time-offset*86400 | eval _time=strftime(_time,"%a %d %B %Y") Because _time is stored in epoch format but displayed in human format you can use the input settings: Field for Label=_time Field for Value=_time The trick for your 2nd dashboard panel is to use a time calculated from the first token. This can be done in the dashboard XML code inside the input definition like this : <change> <eval token="weekago">strftime(strptime($time_tok$,"%a %d %B %Y")-7*86400,"%a %d %B %Y")</eval> </change> As you can see, I substracted 7*86400 seconds to the chosen time to make it 1 week earlier. Then I use both strptime and strftime for the calculation and display. Now I have $time_tok$ shown and stored in human format from the dropdown, and $weekago$ as well in human format. If they are needed in a search for the earliest/latest settings, I'd need to reformat them with strptime. Complete code : <title>Chosen date: $time_tok$ / 1 Week ago= $weekago$</title> <input type="dropdown" token="time_tok"> <label>Pick a date</label> <fieldForLabel>_time</fieldForLabel> <fieldForValue>_time</fieldForValue> <search> <query>| makeresults count=14 | streamstats count as offset |eval _time=_time-offset*86400 | eval _time=strftime(_time,"%a %d %B %Y")</query> <earliest>-24h@h</earliest> <latest>now</latest> </search> <change> <eval token="weekago">strftime(strptime($time_tok$,"%a %d %B %Y")-7*86400,"%a %d %B %Y")</eval> </change> </input>
... View more