Date and Time Ranges
Almost every question in eConnect has a period, and the range picker is shared across modules — so it works the same way wherever you meet it.
Setting a range
Pick from the presets for common periods, or set a start and end directly. Dates and times can be typed as well as chosen, which is faster once you know the format your system uses.
Set the range before filtering. It usually removes more records than any filter will, which makes the effect of each subsequent filter easier to judge.
Choosing a sensible period
The commonest cause of a slow query or an unreadable result is a range far wider than the question needs.
| Question | Range |
|---|---|
| What happened on this shift? | That shift |
| Is this person a regular? | Several months |
| Was this a one-off? | A week either side |
| What is normal for a Tuesday? | Several Tuesdays |
Start narrow and widen if you find nothing. Starting wide and narrowing means every intermediate query is slow.
Time zones
Times are shown in the zone set on your profile, and the underlying records store real instants — so the same detection shows at different clock times to colleagues in different zones.
The dates and times you type into the range popover are in that module's zone as well, matching what the button shows and what the query runs in. A range set for 18:00 means 18:00 where the data was recorded, not 18:00 where you are sitting.
This matters in three places:
- Comparing notes with a colleague elsewhere. Agree which zone you are both quoting.
- Exports. A CSV carries no zone indication — say which one it is in. See Exporting Data.
- Overnight periods. A "night shift" crossing midnight spans two dates; set the range by time, not by picking a single day.
Periods that cross midnight
Set the start on one date and the end on the next rather than selecting a day and hoping. A shift running 22:00 to 06:00 is not "yesterday" or "today" — it is a range across both, and picking a single date silently returns half of it.
Ranges and saved queries
A saved query carries its range with it. That is right for a fixed period — a particular incident, a specific month — and wrong for something you re-run, where you want the range moving with you.
For anything running repeatedly, prefer a relative period so the query keeps answering "yesterday" rather than one particular day. This matters most for dashboard widgets and scheduled reports, which otherwise quietly report the same historical period forever.
Ranges elsewhere
The same picker appears in Semantic Search, aggregations, reports and dashboard widgets. Everything on this page applies in all of them.
What is recorded
The period is part of the audit record of running a query, so a later review can see what range was examined, not merely that a query was run.
Audit record
What eConnect writes to the audit trail for the actions on this page.
QUERY 'POS Events' FROM {start date} TO {end date}; VIEW: 'Events' PAGE {page};