REST API Export Report to a .pbix for archiving

[dthompsonKairos]

I have been assigned with the seemingly simple tack of creating a Logic App to download all the reports in a workspace to their .pbix files.

To Be Clear: This is to download the report file and not an output of the report data to PDF or other format. Even the MS documentation seems to confuse the two. So, the call which does this:

Apparently this is not that hard. Just use Get Reports to return a list of report, throw it into a For Each loop, and use Export Report. Wash, Rinse,. Repeat.

But there are questions:

1. The Export Report action returns a link to where the exported .pbix file has been temporarly stored in Azure. 

    a. How long is this file Kept?

    b. If the action is repeated, is that file overlayed or saved with a  "Copy", _1, or similiar appended to the name?

    c. I haven't a clue as to what PA or Logic App action could be used to then invoke the URL in order to physically save the file. Perhaps it could be put into a Sharepoint document library?

So while the process of getting to the Export Report is straight forward, what happens after is not.

Please Wax Poetic!

Thx

[lbendlin]

1.a) until you run the next export

1.b) overwritten

1.c) definitely not Power Automate since that has a 100 MiB message size limit

What's the point of exporting these files?  Are you hiding the fact that you have no business continuity / version control process?

[dthompsonKairos]

You are correct. There was no existing version control process when I arrived a few weeks ago. My manager thought this was a good approach. I'll be able to dissuade him now citing the limit.

The end goal is just a weekly snap shot of all .pbix files.

Thx

[lbendlin · Accepted solution]

Place your PBIX on a SharePoint. You get version history for free.