Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Why oh why oh why....
The left hand side of the image shows the table result of a Dataflow.
The right hand side shows what I see when I DirectQuery link onto it in Power BI Desktop ( Version: 2.130.930.0 64-bit (June 2024))
Notice that the "awarded" dates are different!
I've no idea why or how.
I initially traced an issue down to SharePoint returning date only columns in UTC with the timezone difference as I'm in the UK and we are currently UTC+1 (aka British Summer Time)
So I just use some Power Query to sort out the datetime to be a date and this shows as expected in the result of the Power Query in the Dataflow.
By the time it is processed in the Service I see a different result.
Surely 2 versions of Power Query are not being used.
1 - by the visual / processing side of DataFlows
2 - the the engine refreshing the data itself
It's even worse than that. There are four different Mashup engines at work - Desktop, Gateway, Service and Dataflows.
Your remedy should be to always only use ISO-8601 UTC datetime strings, and then to leave the rendering up to the end user (who may or may not be on BST)
Naaaaa.
If Microsoft have several mashup engines then they should all return the same output if the M is consistent.
Also it's a date so any time element should be irrevevant.
We'll log it to MS.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
14 | |
13 | |
13 | |
12 | |
12 |