Another way of resolving this would be to add functionality to Create Lists such that dates may be expressed as MM-DD-YYYY HH:MM:SS in the C.L. query. The presence of the time of day information would inform the code which generates the SQL behind the scenes to NOT truncate compared datetime values back to midnight. This would permit the construction of a query like

PATRON Created Date between "11-04-2026 18:15:00" and "11-04-2026 22:30:00"

Even if one has to use Create Lists' JSON view to enter the time of day details, it would provide a workaround.

This is data that exists in the system, on the SQL side of things nearly any date in Sierra is actually a full timestamp. That extra level of detail just needs to be more readily exposed in the tools that most staff have access to, so making timestamps exportable from Create Lists really feels like an easy win.

There was recently an outage of a few hours with our vendor that sends Welcome messages for new accounts. We cannot identify the accounts that did not receive the message because the timestamp is not currently available. We had to generate a list of all accounts created that day and compare with the accounts that received an email. This process would have been much simpler if the account creation timestamp was available.

This would help us tie efforts made at programs where we promote patron registration to actual numbers, help us determine if it's worth the effort. We think we have a lot of people who attend an event but are not cardholders.