Forum Discussion
Full documentation and example for OData.Feed please
You can find documentation about OData.Feed (and all other M language functions) in MSDN. Here's the page for OData.Feed: https://msdn.microsoft.com/en-US/library/mt260868.aspx
Note that you can also find in-product documentation by just typing =OData.Feed (or any other function) in the Query Editor formula bar and hitting enter.
Thanks,
M.
I appreciate the fact that PowerBI includes the docs. That was unknown to me, but then again, the information is identical to the "lacking" documenation on MSDN.
I had found the web page and I was indicating it could use some work.
The link included in your answer is not valid, as it doesn't lead the documentation page I already had found. Here's the one I had located and was commenting on:
https://msdn.microsoft.com/en-us/library/mt260868.aspx
This page contains a somehwat usable description of the fields in the record but includes no examples. Would it be difficultt to get someone to tweak the docs to include exampes, as just about every other PQFL page has? It liternally looks like the team ran out of budget and just stopped writing usable documenation. The record elements are not even in a table as in other documentation pages for PQFL functions.
Specific information it takes for someone to understand the usage of OData.Feed is left out.
Look, for example at the page for XML.Document:
https://msdn.microsoft.com/en-us/library/mt260907.aspx
There, we have complete descriptions of the usage, and we have examples. Developers can use good examples to start from a known good place when customizing usage of a function.
One specific question would be (stating what I asked before) would be to have an explanation of and an example of the query element of the record. I've tried extracting a valid OData query URL portion, like "$top=2", and including that in several forms, and nothing seems to work differently.
If the query string cannot include top=n, then what can it contain?
You see how examples would help allow developers to understand the documentation.
-thanks
-e