Export data from Power BI using Microsoft Flow

Edit 5th May 2019: Unfortunately this method will not work in the Power BI service!

In my last 2 posts I’ve described a way to automatically validate attachments from incoming E-mails. Microsoft Flow would watch for incoming E-mails, that match certain criteria and move their attachments to a dedicated folder. Then it would trigger a refresh of a Power BI dataset, that has been designed to check for errors in those attachments. Data driven alerts in Power BI would indicate if there are errors and trigger a Flow that sends an E-mail back to the sender, informing him that his attachments didn’t meet the agreed criteria.

In this article I will now explain how not just a trigger about the existence of a faulty attachment could be passed back to Flow, but also the corresponding data itself. Therefore I write a query that exports data from Power BI to Flow. But watch out: This is not suitable for very big tables. I experienced timeouts at tables with 300k rows already.

Send data from Power BI to Microsoft Flow

As Chris Webb described in this article, Power Query can create POST requests to a webservice, thereby passing values in the body of the call to the webservice. This allows to export the data from Power BI. With Flow, it is very easy to setup a webservice: Just create a Flow whose trigger is a “When a HTTP request is received” (no further inputs in that step) and add a “Compose”-action with the Body-element in it. Then save the Flow and copy the generated URL:

Setup webservice in Flow that listens for incoming data (export from Power BI)

Power BI

In Power BI, you perform the following steps:

  1. Transform your error-table into a list of records (as that is the format of a JSON-array that Flow likes):
    • row 3: Table.ToRecords(<YourTableName>)
  2. Transform that into a JSON-binary that the Web.Contents-function can digest:
    • row 4: Json.FromValue(<YourListOfRecordsFromAbove>)
  3. Make the Web-call to the copied URL (use Anonymus credentials):
    • row 5-7: Web.Contents(<PasteTheURLFromFlowHere>, [Content=<JsonFromAbove>])
  4. Parse the result and load this query to the datamodel (this is very important, because otherwise the WebCall wouldn’t be made if the dataset is refreshed!):
    • row 8: Lines.FromBinary(<WebCallFromAbove>)

Code to export a table from Power BI to Flow

Back in Flow

Modify the “Compose”-step to parse out the table from the JSON like this:

Next step is to create a csv table:

And export it to OneDrive:

Save csv to OneDrive for Business

I’ve passed the FolderPath and FileName dynamically from Power BI here, but that’s not necessary. Just make sure that the folder is different than the one that contains the original attachments. A trigger will be set on this folder that sends the e-mail back to the sender. So the saving of the original attachment mustn’t trigger this return-email back to the sender already.

Now this sub-flow is completed. In the next steps you will adjust the main flow (like described in the previous post) to attach the generated file to the email.

Adjust main Flow

Task is to attach the stored csv-file to the email that will be sent out to the sender of the attachment. There are a couple of new steps (red) and an adjustment in the “Send email”-step:

Adjustments for the return-attachment

As the query, which calls the web-service will probably be executed twice, I’ve added a wait-step. The time has to fit to the table length, so you might test this for your specific file behaviour. Then the content from the saved file has to be fetched and added in the attachment:

Adjustments in main Flow: Attach e-mail

The last 2 new steps in the flow are similar to the previous ones and simply delete the files from the “return-attachment”-folder. Of course, if you want to keep them in a folder somewhere, you can instead implement a step that moves the file over there, instead of deleting.


As soon as Power Query will be fully integrated in Flow, these tasks don’t need any Power BI-involvement any more: You can do the validations directly in the editor there. Although: Given the current lack of support to parse csv-files in Flow (and the terrible performance of the current workaround), I’m wondering if it wouldn’t be better, if the Power Query connector in Flow would save it’s results to csv-files instead of pushing it back to Flow (a bit like the new dataflows are doing it now). This would allow for mass-data-transformations and forwarding its results, without congesting the Flow-service.

What are your thoughts on this?

Enjoy & stay queryious 😉

Comments (35) Write a comment

  1. Got this error in data source credentials when published to Power BI service.

    Failed to update data source credentials: Web.Contents failed to get contents from ‘https://prod-56.westeurope.logic.azure.com/workflows/346eea9b6717462695ca367562e49f1a/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=e6iSqgGlmOJGOUcEGeuslyUvoAXgzrtL9lyOpnuWPv4’ (400): Bad RequestHide details
    Activity ID: eee3fbcd-d6cb-4639-a701-8ef3108ffad4
    Request ID: 9fd6a5f4-1056-3ae2-d083-abaa425e8f84
    Status code: 400
    Time: Wed May 08 2019 00:35:47 GMT+0500 (Pakistan Standard Time)
    Version: 13.0.9264.166
    Cluster URI: https://wabi-west-europe-redirect.analysis.windows.net


      • Thank you for this wonderful post. It was indeed a breeze a to set it up and I was able to run few flows after the scheduled refreshes. But, suddenly it started through the bad request 404 errors. Nothing is changed in the configs though. Have raised it with PBI community hoping to find a solution.

        Anything else you can think of? Happy to provide more details. Thanks in advance!!



        • Hi Sasi,
          there might have been some changes in the service, that prevent this working now unfortunately.
          I’m not using this in production, so cannot tell from own experience.


  2. Actually it is an Data source credentials error. everything works fine in Power BI desktop but when I upload it to Power BI service and tries to refresh, I got this error. (I used Anonymous credentials for HTTP request.)


    • I’m very sorry, just recognized that I didn’t test this in the service. Unlike the data driven alert, that allows to sign in to SharePoint, there is not such an option for this method.
      That was a bad overlook from my side. Will have to check if it’s possible by using a custom connector for it.
      Very sorry for wasting your time,


  3. Hi Imke,

    Thank you for the suggestion, and I got that working in the desktop and in the service. Very cool and useful stuff!

    I also have a need to export from Power BI to an Excel file (xlsx). I’m struggling to adapt the export to csv concept to fit the need to export to Excel. Any idea what that script or syntax would look like in the Power Query editor?


  4. As Chris Webb described in this article, Power Query can create POST requests to a webservice, thereby passing values in the body of the call to the webservice. This
    …i do not understand the very first step…i have did it till let
    Source = #” Tracker – SAP”,
    ToArray = Table.ToRecords(Source),
    ToJsonBinary = Json.FromValue(ToArray)

    but how to go further


    • You have to add the steps “WebCall” and “LinesFromBinary” like described in the article.


  5. Could you please specify the steps for webcall method to call power bi datasets as i am unable to get the steps for it


    • You’re missing the steps 3) and 4) from the listing in the article above. That’s the last 2 steps in this query:

      Source = #”1_SourceTable”,
      ToArray = Table.ToRecords(Source),
      ToJsonBinary = Json.FromValue(ToArray),
      WebCall = Web.Contents(
      [Content = ToJsonBinary]),
      LinesFromBinary = Lines.FromBinary(WebCall)


      Where “https://prod-123.westeurope.logic.azure.com:443/workflows/….xxxxx….geQ” needs to be replaced by URL from Flow (“When a HTTP request is received” -> “HTTP POST URL”



      • I am entering below mentioned code in “When a HTTP request is received” in flow to generate URL
        Source = #”Tracker – SAP”,
        ToArray = Table.ToRecords(Source),
        ToJsonBinary = Json.FromValue(ToArray),

        [Content = ToJsonBinary]),
        LinesFromBinary = Lines.FromBinary(WebCall)

        but getting error message in the first line as expecting JSON object.

        My question is how to generate this “HTTP POST URL” in flow
        1st step
        Create Instant flow
        2nd Step
        Select “When a HTTP request is received”
        I am entering above mentioned code to get URL
        Kindly correct me below
        how to generate this “HTTP POST URL” in flow


  6. Hello,
    Actually my simple question ..how you are connecting to power bi using http post request..is it that you are doing schema export or or calling power bi web service as this url requires proper codes to call and your codes says it is invalid json code..please assist


  7. It works in Power BI Service. Just mark “Skip test connection” when adding it as DataSource to Gateway Clusters.


  8. Hi there,
    I’ve managed to replicate the same process as above but set to Create file in a sharepoint folder.

    The only problem I’m coming across is that even though I have a daily scheduled refresh configured at specified hours against the dataset, why is it that the flow doesnt trigger also?


  9. This has been working for me except for one thing that I’m still struggling with. Does anyone know how I would return the table back to the query from the function? Right now, after I call the function I’m left with no results (“this list is empty”).


    • Hi Riley,
      because M is a (partially) lazy language, the last step of the export-query has to be the result that the web call that the export does returns.
      Otherwise the export would not be executed.
      But that should not be a problem. Just split the export query at the step which you want to work with further:
      – check the step that follows the one you want to continue with,
      – rightclick mouse and select “Extract Previous”
      – enter a name for the new “staging” query
      – check that query -> rightclick mouse -> reference


      • Ahh. That could work, but I was kind of hoping to do it in a few less steps. I’m building DataFlows to populate Azure AD groups and this would take me from 60+ queries to 120+ queries. Thanks for the suggestion though, and I’ll see how it affects the overall performance of each DataFlow.


  10. Hope you can help. I can add the HTTP request, compose and create CSV file and the query in power bi desktop works but as soon as i add create file i get the error DataSource.Error: Web.Contents (400): Bad Request

    What can i do to fix this?


    • Sorry, no idea.
      You can try to use Fiddler and analyse the web protocols. Just check what Power Query is sending and compare that to the requests from your endpoint.


  11. Hi Imke,
    I used Fiddler and got the error:
    {“error”:{“code”:”InvalidRequestContent”,”message”:”The input body for trigger ‘manual’ of type ‘Request’ must be of type JSON, but was of type ‘application/octet-stream’.”}}.

    In the instruction above its says that you need to add outputs(‘Compose’)[‘BinaryContent’] to the Create CSV but im not allowed to add [‘BinaryContent’].

    Might this cause the error?


Leave a Reply

Die Datenschutzbestimmungen finden Sie hier: / Please find the privacy policy here: https://wp.me/P6lgsG-Rz