Enhanced refresh with the Power BI REST API - RequestId not valid

[BartVW]

hi community

I'm creating a flow to perform a Power BI Enhanced dataset refresh. 

According to the documentation, after doing the POST to refresh the dataset, the RequestId that is returned from the POST can be used to check the status of that refresh.

When I do these steps in Postman, it works ok. I can use the RequestID I get from the POST to then do a GET (as described here in the article).

When I do the same steps in Power Automate (using the same authentication etc), the RequestID I get from the POST is not recognized when trying to the GET Refresh history in the 2nd step.

Would anyone know why this could be?

Many thanks

Bart

(also posted this in the Power Automate community Enhanced refresh with the Power BI REST API - RequestId not valid (powerplatform.com))

[Anonymous]

Hi @BartVW ,

You can refer the following links to refresh Power BI dataset:

Refresh your Power BI dataset using Microsoft Flow | Microsoft Power BI Blog | Microsoft Power BI

How to Refresh Power BI Dataset Using Power Automate

Best Regards

[BartVW]

hi @Anonymous 

Your link describes the normal (non-enhanced) dataset refresh. The problem is that this only triggers the refresh, but doesn't provide any feedback on whether it was succesful or not. 

The enhanced data set refresh allows to do this by doing the process in 2 steps: first call the dataset refresh api using POST and including a body to trigger it as an enhanced refresh operation, and then call the data set refresh api using GET to check the status of the refresh, using the requestId from the first step (as described in the documentation link I provided),  but for some reason it doesn't work as documented in Power Automate (and does work OK in Postman).

So hope you or anyone else has an idea how to resolve this.

Thanks

Bart

[BartVW · Accepted solution]

In the meantime I found the reason for above behavior, thanks to Chris Webb's blog here.

Turning off the Asynchronous Pattern option in the Settings dialog of the HTTP action did the trick for me.