By using this website, you agree to our Terms of Use (click here)
Has anyone here upgraded to at least 2020 R1 who uses the OData feeds in things like Power Query for Excel or for Power BI?
I am running into a serious problem where a few things have changed:
1) The OData feed now pulls in every column - even those set to inactive in the results grid
2) The Odata feed pulls in extra columns for every join - RefNoteID column and an Attribute column - in some cases
3) Also pulling in any masked fields - so for example, if you add "InventoryID" it pulls in both "InventoryID" and "InventoryCD"
There may be others, but this is causing some havoc in my reports - anywhere where I had any appended tables especially, but generally everything looks like a total mess now.
Anyone else run into this?
Thanks!
I should also note that we haven't launched 2020 R1 yet - we're just in UAT phase currently.
Combing through the help docs, just saw this:
"Through OData, you can view the list of fields in exposed inquiries. The field names in the list are changed according to the OData specifications, as described in Supporting the OData Specifications earlier in this topic. The list of fields also includes the key fields of the tables used in the generic inquiry if these key fields have not been added to the Results Grid tab of the Generic Inquiry (SM208000) form for the generic inquiry."
Looks like they've made this drastic change. Although this doesn't mention anything about active/inactive fields in results grid.
I have experienced #2 and #3, but not #1.
Adding this parameter to the URL will control the columns I believe. Works in PostMan anyway!
$select=<list of columns you actually want separated by commas>
https://myurl.com/OData/tenant/GIName?$format=json&$select=ReferenceNbr,AdjgRefNbr, LineNumber
Rich