teableio
Exact DateTime Filter Always Ignores Time Component
Describe the bug When creating any sort of filter that uses an exact DateTime, the filter always ignores the Time component.
https://github.com/user-attachments/assets/be23ca87-c63c-4628-b407-cf4acf3a34ee
Expected behavior I expect the Time component of an exact DateTime filter to be used correctly.
** Client (please complete the following information):**
- OS: [e.g. macOS]
- Browser [chrome]
- Version [139.0]
Platform (Please tell us which deployment version you are using) [docker-standalone]
Note: I just upgraded to the latest version of teable 0.4.0-alpha+1.9.1-build.371 and this problem still exists.
Filter data accurate is day, if you want to filter by hour or minute. It's good way to set a formula field to extra the hour or the whole date string then filter accurately.
Filter data accurate is day, if you want to filter by hour or minute. It's good way to set a formula field to extra the hour or the whole date string then filter accurately.
Hi @caoxing9 , understood. Yes, there's a workaround where I can create a formula to extract out the hour or minute components from the timestamp and then apply a filter.
Still, long-term, it would be helpful if the default timestamp filter actually used the HH:MM component so that I don't need to use this workaround. Thanks!