Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi all,
I am trying to make a new table that contains the following columns:
- Dates (a calendar column from the "Calendar" table)
- Id (just a bunch of IDs from the "Deliverable" table)
- Approval Planned (dates from the "Deliverable" table)
- Approval Actual (dates from the "Deliverable" table)
Note that all rows in the "Deliverable" table contains an ID, but not necessarily dates in the "Approval Planned" and "Approval Actual" columns.
I have matched the columns "Dates" (from "Calendar" table) and "Approval Planned" (from "Deliverable" table), by using the "Left Outer" Join Kind. Afterwards, I expanded the new column called "Deliverable" as this was a table - and included only "Id", "Approval Planned", and "Approval Actual".
This creates the below result in the Query Editor, which is exactly what I want: A lot of rows with only the date column filled out, with only rows with a "Planned Approval" value showing up in the other columns.
So far so good. I close the query editor and go back to my report.
And that is when the problem emerges. When I view the table in the data view, it looks like this:
Now, all the rows with the "Planned Approval" column filled out are duplicated and moved to the bottom of the table. At the same time, they disappear from their original positions. I want it to look like in the Query Editor...
What am I doing wrong, or is there a way to fix this? Any help is highly appreciated! 😁
Solved! Go to Solution.
You're not doing anything wrong. This looks like standard behaviour to me. I don't see any duplicate rows - I see some rows which have the same approval date.
The order of rows in data view isn't really important - it's controlled by the storage algorithms behind powerbi unless you override it by sorting from the column headers
You're not doing anything wrong. This looks like standard behaviour to me. I don't see any duplicate rows - I see some rows which have the same approval date.
The order of rows in data view isn't really important - it's controlled by the storage algorithms behind powerbi unless you override it by sorting from the column headers
Alright, perfect!