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.
kushanNa
Super User
Super UserMaybe this is happening becuase you have blank / incorrect format / error values in APP table
for an example following is the sameple APP table with 3 values , 1 correct and two incorrect