![power bi desktop scheduled refresh power bi desktop scheduled refresh](https://i0.wp.com/blog.crossjoin.co.uk/wp-content/uploads/2020/04/IncrementalConfig.png)
![power bi desktop scheduled refresh power bi desktop scheduled refresh](https://docs.microsoft.com/en-us/power-bi/connect-data/media/refresh-data/refresh-status-warning.png)
![power bi desktop scheduled refresh power bi desktop scheduled refresh](http://www.cittabase.com/wp-content/uploads/2019/04/PBI_ScheduleRefresh_Setting.gif)
To perform different operations depending on a dataflow or dataset, we need the switch operation. We perform this action with the earlier created custom connector for the Power BI REST API. Because of that, we want to perform a different operation in the flow depending on the item. In the flow setup we make use of the Power BI REST API, which has a different API call for dataflows then for datasets. Looking at the input values for the Power BI REST API, we need at least the groupId (workspaceId) and the dataflow or dataset Id in order to trigger the refresh. The easiest solution for this, is to simply create a SharePoint list for that. Since we decided to have one central place to manage all our Power BI refreshes, we need to store the schedules somewhere. Besides the dataset, we can call a dataflow refresh as well now. Ida Bergum, wrote a great blog on creating a custom connector for Power BI API calls in Power Automate.īased on this custom connector setup, we will be able to call a whole lot of different action, which are supported by the Power BI REST API. The custom connector can help to keep our flows simple and clean and re-use API calls in different flows as well. However, this requires a lot more work (and rework), every time you want to call this API. In Power Automate, you can create HTTP calls for every API call you want to do as well. To solve this challenge, we created a custom connector, which enables us do everything the Power BI REST API supports. For example, dataflows can’t be triggered to refresh based on these actions. Looking at our use case, we want to do a lot more than only triggering a dataset to refresh. The native actions only support the following operations: For the managed refresh flow, we need a Power BI action to be triggered based on other settings.Ĭurrently, the native Power BI actions are in preview, but also a bit limited to be honest. Second, there are also Power BI related actions available in Power Automate. This interaction is only the trigger for a flow.
![power bi desktop scheduled refresh power bi desktop scheduled refresh](https://i.stack.imgur.com/qe4gy.png)
First, is event triggered actions, where a flow starts running if a defined value is exceeded. Power Automate has two different ways of interacting with Power BI. Power Automate custom connector, to perform an API call easier to the Power BI REST API.Power BI REST API, to trigger the refresh for both dataflows and datasets.SharePoint lists, so set and save our refresh schedules.Power Automate, to trigger the right (API based) actions on a recurrence.In this blog I will elaborate on how you can setup your own centrally managed refresh policies by using: However, there is already an idea listed on the Power BI forum (please vote for it!), we can easily build a solution ourselves to manage all our refreshes. Managing all of them in one central place, will be a very welcome feature! There is no place to have a clear overview of all refreshes scheduled with your own account or a service account. At least, it is easier to centrally manage the dataflows when you are working from a center of excellence or competence center perspective.Īll content which require a refresh, both dataflows and datasets, can only be managed from the workspace perspective. Working with service accounts can help us here. Since these refreshes can only be managed by the owner, this limits the rest of my colleagues from updating the scheduled and maintaining the solution. As a Data & Analytics consultant, working on tons of different projects, it is very likely that I’m the creator and owner of a whole lot of dataflow and dataset refreshes.