Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi I am receiving the following error when I try and link a SharePoint site to Power BI
DataSource.Error: We couldn't parse OData response result. Error: A null value was found for the property named 'Actionee1Id', which has the expected type 'Collection(Edm.Int32)[Nullable=False]'. The expected type 'Collection(Edm.Int32)[Nullable=False]' does not allow null values.
Details:
DataSourceKind=SharePoint
DataSourcePath=https://#######.sharepoint.com/BD/_api/Web/Lists(guid'#####-####-###-###-#####')/Items
I have seen this error before, but previously I could delete the column in question, unfortunately, this time I cannot
the field in question is a people field which is non mandatory
any help would be gratefully received
Kindest regards
Jack
Solved! Go to Solution.
I changed the ApiVersion from 15 to 14 in the Query Advanced Editor, and it works now 😃
let
Source = SharePoint.Tables("https://###.sharepoint.com/teams/Team020/", [ApiVersion = 14]),
ProjectList = Source{[Name="ProjectList"]}[Content]
in
ProjectList
Hi,
can you please give any more specific information on how we could do that? 🙂
Hi lelenko,
What is your problem about? Do you struggle with extraction data from SPO list, which has a many lookup and multi-lookup fields? Here "many" means more then threshold.
BR, Sergey
Can anyone give imformation on how we could do that?
I am getting this error: DataSource.Error: OData: The feed's metadata document appears to be invalid. I noticed other people are getting it. Is there any other solution to this problem that might work? I have been trying to work around the error all morning!
I got the same error too
I am getting this error: DataSource.Error: OData: The feed's metadata document appears to be invalid. I noticed other people are getting it. Is there any other solution to this problem that might work? I have been trying to work around the error all morning!
When I change ApiVersion to 14, SharePoint.Tables() function return nothing !
So I cannot use this workaround. Any other ideas ?
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>
= OData.Feed("https://XXXXX.sharepoint.com/sites/pop/_api/Web/Lists(guid'abcd-efgh-ijkl-mnop-qrst')/Items?$select=...")
You can stay with version 15 API.
Hi @djeepy1!
Look at my script (automaticaly generated):
let
Origem = SharePoint.Tables("https://xxxxxxxxx.sharepoint.com/gestao/", [ApiVersion = 15]),
#"xxxxxx" = Origem{[Id="xxxxxx"]}[Items]
in
#"xxxxxx"
Where I have to put your command?
Tks.
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
where
Notice I added feedback to my previous comment. I do not know if it applies to your error / context.
Jean-Pierre Riehl
Tell me please
Why does not this request?
let
soursOData = Data.Feed("https://<app web url>/_api/web/Lists(guid'DEE5D045-C8AB-4878-B3F1-0D814EBF648E')/Items?$select=TextMonth,TextQuarter")
in
soursOData
Error OData.Feed
P/S/
This code is working in the browser
This error message will been given when a multiple user or multi choice field is empty. When all the fields are filled this error message will not been given
Thanks for the help. I went into the SahrePoint list and added and N/A choice then did quick edit to update all empty values to N/A and it worked!
Worth Noting:
We completely removed the column in the Power BI query and still got the error. We removed all null in the query editor and got the error as well. Only thing that worked was editing the column in SharePoint.
Any news on when this bug will be fixed? To be clear it affects both the Power BI desktop client as well as Excel (Power query).
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.
User | Count |
---|---|
16 | |
10 | |
9 | |
9 | |
8 |
User | Count |
---|---|
23 | |
17 | |
12 | |
12 | |
12 |