Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
When enabling RLS and using DirectQuery within Power BI, the timestamp field is being truncated/obfuscated, resulting in inaccurate query matching.
Details
A precise timestamp such as:
2024-11-05T08:00:03.2710808Z
Is altered by DirectQuery to:
2024-11-05T08:00:03.0000000Z
Because of this, DirectQuery truncates timestamp statements such as:
| where time == datetime(2024-11-05T08:00:03.0000000Z)
return no results, as the original timestamp no longer matches.
Impact / Workaround
We are required to apply a workaround using binning to force alignment:
| extend time = bin(time, 1s)
This behavior affects query accuracy and adds unnecessary transformation logic to reports.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.