Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
CmdrKeene
Helper IV
Helper IV

DataSource.Error connecting to SharePoint 2010 list

This failure when trying to connect to a list on SharePoint.  The list has a variety of field types, like People, Choice, and Multi-Line text fields.

 

DataSource.Error: We couldn't parse OData response result.  Error: An error was read from the payload. See the 'Error' property for more details.
Details:
    DataSourceKind=SharePoint
    DataSourcePath=http://teamsharepoint/sites/teamsite/_vti_bin/ListData.svc/Upgrades

 

Please help, I need to connect this list to PowerBI.


CmdrKeene
1 ACCEPTED SOLUTION
CmdrKeene
Helper IV
Helper IV

I was having this same issue on two particular lists on our SharePoint 2010 site. I read some posts that mentioned it could be caused by lookup fields, but neither problem list had such fields. Other posts mentioned people/person fields, I had them but I ruled that out as well.

 

So I turned to the calculated columns in my list. I had three. I set each one to just a calculation of "=1" and saved, and noted that the ListData.vsc started working!  While two of the calculated fields had much more advanced formulas, after process of elimination I determined that this calculated field is the one causing the problem for me:

 

Field Name: "Expected Launch Date"
Field Formula: =IF([Call 2 Completed]=0,"TBD",[Call 2 Completed]+7)
Return Type: Date Only

 

You might see the problem now -- my simple "IF" formula is returning text "TBD" string for a column with a type that must return "Date Only". So, I changed the formula to the following and my list is still working now.

 

New Formula: =IF([Call 2 Completed]="","",[Call 2 Completed]+7)

 

Read as "If [Call 2 Completed] is null, use null. Otherwise, add 7 days to [Call 2 Completed]"

 

Anyway I think I'm good now.


CmdrKeene

View solution in original post

1 REPLY 1
CmdrKeene
Helper IV
Helper IV

I was having this same issue on two particular lists on our SharePoint 2010 site. I read some posts that mentioned it could be caused by lookup fields, but neither problem list had such fields. Other posts mentioned people/person fields, I had them but I ruled that out as well.

 

So I turned to the calculated columns in my list. I had three. I set each one to just a calculation of "=1" and saved, and noted that the ListData.vsc started working!  While two of the calculated fields had much more advanced formulas, after process of elimination I determined that this calculated field is the one causing the problem for me:

 

Field Name: "Expected Launch Date"
Field Formula: =IF([Call 2 Completed]=0,"TBD",[Call 2 Completed]+7)
Return Type: Date Only

 

You might see the problem now -- my simple "IF" formula is returning text "TBD" string for a column with a type that must return "Date Only". So, I changed the formula to the following and my list is still working now.

 

New Formula: =IF([Call 2 Completed]="","",[Call 2 Completed]+7)

 

Read as "If [Call 2 Completed] is null, use null. Otherwise, add 7 days to [Call 2 Completed]"

 

Anyway I think I'm good now.


CmdrKeene

Helpful resources

Announcements
Power BI DataViz World Championships

Power BI Dataviz World Championships

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!

December 2025 Power BI Update Carousel

Power BI Monthly Update - December 2025

Check out the December 2025 Power BI Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors