Forum Discussion

JackWS's avatar
JackWS
New Member
10 months ago

SharePoint Online List connector (Implementation 2.0) only returns first 200 rows

When connecting to SharePoint Online lists using SharePoint.Tables(..., Implementation="2.0"), Power Query retrieves only the first 200 items and ignores the @odata.nextLink token.
Implementation 1.0 handles paging correctly.
This limitation makes 2.0 unusable for lists > 200 rows.
Please update the connector to follow @odata.nextLink automatically or allow users to configure page size and paging behaviour.

2 Replies

  • Hi JackWS ,

    Thanks for posting in Microsoft Fabric Community.

    Apologies for the inconvenience.

    The behavior you're seeing with SharePoint.Tables(..., Implementation="2.0") is consistent with known limitations.

    If you need to retrieve all rows from large lists using Implementation 2.0, you can consider using a custom paging solution with List.Generate. A detailed walkthrough was shared in a related discussion and can be found here: Solved: Re: Retrieve SharePoint Online list data - v2.0 co... - Microsoft Fabric Community

     

    In addition to the paging issue, Implementation 2.0 is subject to the SharePoint Online List View Lookup Threshold. If your list includes more than 12 lookup or person columns, the query may fail or return incomplete data. Creating a view with fewer than 12 such columns and connecting to that view can help avoid this.

    Power Query SharePoint Online list connector - Power Query | Microsoft Learn

     

    There’s also a URL length limitation (~2,100 characters) when using OData.Feed or REST-based connectors. Exceeding the character limit results in a 401 error. To work around this, start with the root endpoint and apply filters inside Power Query.

    Power Query OData Feed connector - Power Query | Microsoft Learn

     

    If the available workarounds don’t meet your requirements, I recommend raising this in the Issues - Microsoft Fabric Community or the Fabric Ideas - Microsoft Fabric Community so it gets more visibility. That helps the product team prioritize fixes and ensures others facing similar limitations can track progress or contribute feedback.

     

    Hope this helps. Please reach out for further assistance.

    Thank you.

    • v-veshwara-msft's avatar
      v-veshwara-msft
      Community Support

      Hi JackWS ,
      Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.

      Additionally, if you have submitted this as Issue or Idea, please feel free to share the link here so others in the community can upvote it. With enough support, Microsoft may consider it for future implementation.

      Thank you.