Yes this work around works but we can hardly teach users how to do this workaround without getting a lot of issues. This really needs to be resolved as there is so much potential in getting nice reports and dashboards from data stored in SharePoint.
Is there any workaround without using the API 14? IF I use that, I don't have my custom lists, those only show up if I am using API 15 which in turn gives me the same error but for another property.
When I change ApiVersion to 14, SharePoint.Tables() function return nothing !
So I cannot use this workaround. Any other ideas ?
I've tryed to chance the version 15 for the 14 and this another error ocurred:
Expression.Error: A chave não correspondeu a quaisquer linhas na tabela (In English: The key does not match any rows in the table)
Has someone any idea about this?
I found a workaround discussing with a SharePoint colleague. You can explicitly define fields you want to get and exclude the one that generate error.
add this parameter on OData query => $select=<fields comma-separated>
You can stay with version 15 API.
You have to use OData.Feed function instead of SharePoint.Tables to reach your list.
I guess this should be :
let origem = OData.Feed("https://XXXXX.sharepoint.com/gestao/_api/Web/Lists(guid'yyyyyy')/Items?$select=zzzzzzz") in origem
Notice I added feedback to my previous comment. I do not know if it applies to your error / context.
Find out how to participate in the first Power BI 'Can You Solve These?' challenge.
Get your latest community news and announcements.
Join us for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.
Each week, complete activities and be qualified in the drawing for cool Power BI Swag.