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.
on:
Default format string locale for dates and numbers...
KevinChant
on:
Issues with changing the workspace ID when version...
mattlee
on:
Default Locale and "None" Display Units should be ...
on:
app.powerbi.com down?
on:
Template App "Microsoft 365 Usage Analytics" faili...