Forum Discussion
HTTP POST query sends out duplicate requests
- 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).
Hello crossover ,
I'm afraid, but at least to my knowledge, you cannot circumvent the duplicate requests. This is why you shouldn't use PQ to write back into SQL databases for example, although the language provides the commands to do so. Problem is, that the writes would be executed twice.
I don't have a reference to the explanations for this behavious at hand, but they can be found under the SQL writeback issue on the web.