The URL itself is: is the name of the capacity The request is a POST request, and all that it requires is a single URL.You must provide 3 configuration values for it to work. The HTTP step calls into Azure to start the capacity. In the example above, the process runs every day at 2:50 AM You can set the recurrence to a number of time periods, and the run time will be based on that start date/time. The recurrence step will kick off the run on a scheduled basis. Logic app to start the capacity and refresh a dataset
![powerbi paginated report builder powerbi paginated report builder](https://docs.microsoft.com/en-us/power-bi/paginated-reports/media/report-builder-shared-datasets/power-bi-report-builder-query-results.png)
![powerbi paginated report builder powerbi paginated report builder](https://i2.wp.com/www.fourmoo.com/wp-content/uploads/2018/11/110818_0653_PowerBIRoun1.png)
Once created, we will add a schedule trigger, an HTTP action, and a “Refresh a dataset” action. The steps involved in doing so can be found in this introductory document. Starting and RefreshingĬreating an Azure Logic app is relatively straightforward. It should be noted that the capacity must be created in the same tenant as the Power BI service itself. Once created, any relevant workspaces can be assigned to this capacity. It is therefore important to select the “Change size” link and choose a size that is A4 or greater. In Azure, the service is called “Power BI Embedded” and detailed instructions for creating it can be found in this document.Īlthough there are 6 possible sizes to choose from, paginated reports in the Power BI service require an A4 capacity at a minimum. Prior to doing any of this, you will need to create a Power BI dedicated capacity in Azure. Optionally, further automation can run on the destination inbox to deliver the report to alternate locations, such as a SharePoint library, etc.
![powerbi paginated report builder powerbi paginated report builder](https://docs.microsoft.com/en-us/power-bi/consumer/media/paginated-reports-view-power-bi-service/power-bi-paginated-report-in-service.png)
Ideally this should be less than a hour after the capacity was started in step 1, given the hourly billing increments. Another Logic App runs on a schedule that allows for both the refresh of the data in step 2, and the report to be rendered in step 3, that pauses the capacity.On a schedule that allows for the dataset above to be refreshed, the report schedule runs and delivers the report to the destination addresses.Note that this is only necessary if the report’s data souce is a Power BI dataset. The Logic app uses the “Refresh a dataset” Power BI action to initiate a dataset refresh.The Logic App runs on a schedule, and starts the dedicated capacity by calling the Power BI API from an HTTP action.An Azure logic app uses the same set of actions that a Flow in Power automate does, but is a little more flexible in its permissions model. The solution will consist of an Azure logic app, and Power BI paginated report scheduling. in order to minimize the cost of the solution, we want the dedicated capacity to run as little as possible. as of this writing, there is no API call available to render a paginated report on demand, so we will rely on the scheduled subscription capability. In our scenario, we have a paginated report that uses a published Power BI dataset as a data source. Matt Allington has a post that outlines this concept in great detail: Affordable Power BI Premium for Small Business. If the capacity can be started, perform a task, and then stopped, then you will only be billed for the time used to perform the task in question.
![powerbi paginated report builder powerbi paginated report builder](https://d365update.com/wp-content/uploads/2021/02/DataversePaginatedReports.jpg)
The “A” SKU is of particular interest, because unlike the other two SKU types, it is billed in hourly increments as opposed to monthly. For a detailed discussion of the different dedicated capacity SKUs, see my older post Understanding the Power BI capacity based SKUs. The different SKUs have different features and capabilities, but for the purposes of this article, they are functionally equivalent. Premium is certainly one of those ways, but the Azure (A) SKU and the EMbedding (EM) SKU are two others. More accurately, this option is called “dedicated capacity”, and there are a number of different ways to use dedicated capacity. The term “Premium” is often used to describe the resource (as opposed to user) based licensing option in Power BI. This article describes a pattern that will help minimize the cost of using paginated reports for subscriptions. Unfortunately, for the moment at least, paginated reports require the use of a dedicated capacity, which can be cost prohibitive for some. Paginated reports can be exported to multiple document formats, and those exports can be scheduled and delivered via email. Paginated reports in Power BI offer a rich set of capabilities for printing, and the generation of report documents.