Odata Paging Resulting in Blank Record

[Luke-Bongiorno]

I suspect I have a problem with an Odata API and paging. 

When I refresh my data model in Power BI desktop, I find that one of my OData queries has returned 5001 records (out of a possible 8347 that I know reside in the DB). Our Odata API implements server paging with a page size of 1000 items. This would seem to imply that Power BI is correctly requesting additional pages from the service. However, after, I assume, requesting 5 pages (I have 5001 records returned), something occurs that results in a blank record (the 5001st record is simply a blank record) and the retrieval stops, though I dont receive an error.

I only realised there was an issue as, when attempting to create a relationship, the creation falied as there were NULL values in an ID column (the 5001st record is the culprit there).  

Woudl anyone have any thoughts on what I should be looking for or useful steps to help debug this. 

Thanks

Luke

[Greg_Deckler]

I'm not sure it's a "bug". I ran into this at a customer that was getting information out of Project Online from Power Query. My understanding at the time from MS was that this was "by design". However, I got the impression that it was a limitation on the Project Online side. Let me check my notes.