When a dataflow runs long or has an error, you have to manually go to the dataflow settings, refresh history and download the CSV for more information. For appropriate refresh monitoring and trending, can we have a method that will retrieve the details of this CSV using the refresh requestId.
Thanks
4 Comments
- lillyg1New Member
Agreed, we have an automated process that scrapes metadata vis REST API calls for both Datasets and Dataflows refresh history. It's frustrating that the Dataset refresh history includes the Failure Reason when a Dataset fails, but Dataflow API call for Transaction History does not include the Error reason. This would be hugely beneficial and make the REST API an actual useful tool for notifications etc...
- ImkeNew Member
Fully agree!
For me, it's important to get the number of rows refrehsed for each (even successful) dataflow refresh.
This allows me to monitor for changes that might require automatic alerts.
- gbrueckl1New Member
please also expose this information via APIs so it can be viewed by other tools as well and not just in the Power BI web UI
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Auto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv50 minutes agoNew MemberNew3Views1like0CommentsAdd a Close or “Return to previous page” button to Semantic Model Security and Settings pages
When updating RLS group assignments through Semantic model > Security, there is no consistent in-product Close or Done button that returns the user to the previous workspace view. The browser Back b...Kalaiselvan3 hours agoFrequent VisitorNew2Views0likes0Comments