Forum Discussion
Load Performance when adding/adjusting SharePoint List Version History
Super UserDo Not Sort. (If you can)
Sorting is breaking folding.
Power BI doesn't care if Power Query sorted the data. It's wasted effort.
Unfortunately, sorting is essential part in my approach to identify the first version where the status was modified.
In the end, I'm only interested in the modified date of items when the status field was set from xxx to "Done" for the first time (as in the current list, no actual dates are maintained).
As I'm loading all item versions, I then do the following steps:
- Filter for only for status "Done"
- Sort version lable asc
- Buffer the table after sorting to keep sorting
- Remove duplicates on item id
At the end, I just join the date via ID to the current list and lable it as "actual completion date".
Appreciate any tips on improved approaches as I'm fairly new to PowerBI and right now my full load took about 40min.
- lbendlin
Instead of doing this in Power Query, use the ODATA connector to filter the results directly in SharePoint.
No idea if this will be any faster though - also depends on the indexes in your SharePoint list.
