Forum Discussion
CLOCK Table Filtering
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.
Thankyou, Deku, kushanNa, for your response.
Hi JavierLopezFALP,
We appreciate your query posted on the Microsoft Fabric Community Forum.
Kindly find attached the screenshot and PBIX file, which may assist in resolving the issue:
If our response has been helpful, we would be grateful if you could mark it as the accepted solution and provide kudos. This will benefit other community members who may have similar queries.
Should you have any further questions, please do not hesitate to contact the Microsoft Fabric Community.
Thank you.
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.