Forum Discussion
Solved
CLOCK Table Filtering
Greetings. I've got a growing appointments table (950k+, since 2023, well over 2 milllion if I up to 2021), for which I need numerous flags that depend on the appointment time. In order to reduce...
I figured it out. Turns out that the date_time had miliseconds precision. But because extracted the data as datetime, the format within PBI gave no clue about it. And the decimals remained even after "splitting" the time value.
Whereas my Clock_Table had "integer values behind" each time value.
I solved i with
cast (date_time as datetime2(0))Thanks for your input.
Deku
Super User
Super UserYou also need the corresponding binned time in the appointment table to join on.
The associates ones look like they just happen to fall on the exact times in your clock table
For example a row in the appointment table with a time of 12:01 should either have a key of 12:00 or 12:15