Forum Discussion

crossover's avatar
crossover
Advocate I
4 years ago
Solved

HTTP POST query sends out duplicate requests

Hi all!   While I realize it's predominantly a PowerBI board, I'm working in Excel 365 environment. Still, I expect it to be an M / Power Query issue. Big thanks to ImkeF and her Thebiccountant blo...
Need Help
  • ImkeF's avatar
    ImkeF
    4 years ago

    Hi crossover ,

    I don't think that MS considers this as a bug: The first query is used to fetch data that is necessary to create the query execution plan. The 2nd to fetch the data itself.
    So at least in the query editor, these 2 steps will always have to happen. 
    I don't know why the first step is still needed when the data will be loaded to the model or with dataflows to the storage. At least not with static datasources. (Thinking of "stored procedure" for Power Query here ... this would definitely be nice to have).

     

    Also, I haven't tested if Python or M-scripts will also be executed twice. That could be a nice workaround - although I don't like the limitation of a personal gateway here (and that is not supported in Excel).

     

ImkeF's avatar
ImkeF
Community Champion
4 years ago

Hi crossover ,

I don't think that MS considers this as a bug: The first query is used to fetch data that is necessary to create the query execution plan. The 2nd to fetch the data itself.
So at least in the query editor, these 2 steps will always have to happen. 
I don't know why the first step is still needed when the data will be loaded to the model or with dataflows to the storage. At least not with static datasources. (Thinking of "stored procedure" for Power Query here ... this would definitely be nice to have).

 

Also, I haven't tested if Python or M-scripts will also be executed twice. That could be a nice workaround - although I don't like the limitation of a personal gateway here (and that is not supported in Excel).