Internal Server Error while importing SharePoint Online List

[Syndicate_Admin]

I need to import a SharePoint Online List with Collection values, so I need to use ApiVersion 14.  Recently, this stopped working and started giving errors.  I'm not sure if it's relevant, but the list shows up as "TeamTracking" with ApiVersion 14, but "Team Tracking" with ApiVersion 15 (but cannot be loaded due to the Collection type).

DataSource.Error: SharePoint: Request failed: The remote server returned an error: (500) Internal Server Error. (An error occurred while processing this request.)
Details:
DataSourceKind=SharePoint
DataSourcePath=https://microsoft.sharepoint.com/teams/XXX
SPRequestGuid=9e70b79d-1049-0000-4e50-6e555bc44da6
Url=https://microsoft.sharepoint.com/teams/XXX/XXX

[Syndicate_Admin]

been ages but same issue today

[Syndicate_Admin]

Still same issue no response or resolution.   I am seriously thinking moving out of sharepoint to some other source. 

@microsoft :  Please fix this issue.  This seems like a bug, there are many threads around this issue but no resolution yet to this problem.  This is happening to specific sharepoint site and not for all.  

[Syndicate_Admin]

Hi everyone!

I was having the exact same issue with Sharepoint server 2013, and connecting using the Sharepoint list connector (Sharepoint.Tables, ApiVersion 14 in Power Query editor).

My table was working fine with the version 15 of the Api but would not work for the Version 14, which I need so dates stay the same as in Sharepoint.

My solution (it may not be everyone's case but I hope this helps someone else too) was to delete a Calculated column, which in this case gave as result html and icons which where veing queried from a library in the site.
Again, this may not be everyone's problem but it definetely is one of the possible causes, so it is worth checking 😉

[cwarr]

Somewhat belated, but here is my workaround. In my case I needed to load the files from a SP Folder and be able to use the create/update dates in local (AUS) format. Using ApiVersion 15 resulted in parse errors on the date columns because they are not loaded with local format, so any day number > 12 is invalid. Using ApiVersion 14 loads the dates in the correct local format but causes internal Server Error 500. What I noticed was the error appeared as a row after the last row of filenames in the table. But unfortunately you cannot remove this row with a Table.RemoveRowsWithErrors statement (I guess because it is not really a row in the table). It occurred to me that I might be able to load the TopN rows with ApiVersion 14, where N is simply the number of rows that I determine using a Table.RowCount statement that uses ApiVersion 15. A tad convoluted, but bippity boppity boo, all my rows were loaded without an error, albeit without last access date:

let

    #"SP Folder" = "<your folder>",

    Source = Table.FirstN(SharePoint.Files(#"SP Folder", [ApiVersion = 14]), Table.RowCount(SharePoint.Files(#"SP Folder", [ApiVersion = 15])))

in

    Source

[DanWestwood]

Hello did you get any response to this?

[cwarr]

Hi Dan, no, no reply. Not that I was expecting one...

[Anonymous]

i tried here apiversion 15 , but problem is which is lookup columns , not showing any options like date,title ..etc , i feel like segregated entire data into different tables , i just convinced to my managers what are limitations in bi

[Anonymous]

more then 5k records , we can approach odatafeed or web connectors , but not sure these connectors how much satisfy your requirements