Forum Discussion
Web.Headers using MS Graph to handle (expected) HTTP-errors seems not possible. Any suggestions?
Thanks ams1 for your reply!
The first link confirms using web.contents is not capable of manual handling error statusses using ManualStatusHandling. Therefore I hope using an alternative way will solve my problem, like using Web.Headers. But again, it seems Graph does not support the use of the Web.Headers-function... but I don't understand why, or am I doing something wrong?
Extensions are able to use the ManualStatusHandling option with status codes 401 and 403, which is not something that can be done in Web.Contents calls made outside of a custom data connector (that is, directly from Power Query).
Also the second link does not give an answer to the issue. It refers to the following site, where in the comments Ricardo writes the exact same situatie 😞
- ams13 years ago
Responsive Resident
Yeah, with the links I wanted to confirm if that is the feature you want - if that's the case I also think it's not possible in normal PowerQuery.
Often when someone asks "do you support that feature", you tend to say "no" without asking "why do you need that feature/what is the problem you want to solve using that feature?".
So if you can share a bit more details regarding the problem you want to solve with "web.headers"/error handling, maybe the community will say "Oooo, if you actually want that, then you can do it with another feature from PowerQuery..." 😊
BTW there was a recent question ref MS Graph, don't know if you saw it/if it might help you somehow:
https://community.powerbi.com/t5/Power-Query/MS-Graph-ODatalink-paging/m-p/3079980#M98042
And finally: MS Graph and PowerQuery is doable, but... -> https://learn.microsoft.com/en-us/power-query/connecting-to-graph