SharePoint Online Lists connector Implementation 2.0 - Power BI service refresh bug

[alpol2000]

Hello,

I have found a bug with the SharePoint Online Lists connector Implementation 2.0.

I have a SharePoint List with 651 records.  In SharePoint Lists I have created a View of this list filtered to 49 records and set this as the Default View.

When I connect to the List via Power BI Desktop, using the SharePoint Online Lists connector Implementation 2.0 and selecting View Mode "All":

I see 651 records in Power BI Desktop before and after each refresh in Desktop. 

When I publish to the Power BI Service from Desktop I still see 651 records. 

However, after I refresh the Semantic Model in the Power BI Service, I only see 49 records.  I have checked and they are the same 49 records as in the filtered view that I created in SharePoint and set as the Default View.

This does not happen if I select the SharePoint Online List connector Implementation 1.0.  

I am aware there are other workarounds like setting the All Items view of the List as the Default view in SharePoint or using the web connector to connect to the SharePoint API.

Is this bug with the SharePoint Online List connector Implementation 2.0 known?  Is a fix in the works?

Thank you! 

[v-priyankata]

Hi @alpol2000 

Thank you for reaching out to the Microsoft Fabric Forum Community.
@vigneshkumarcvk Thanks for the inputs.

In this case please reach out to support team to help on this.  Kindly raise a support ticker here How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn.

Thanks.

[alpol2000]

thank you @vigneshkumarcvk for confirming this is a known issue to the product team.

[vigneshkumarcvk]

Hi @alpol2000 ,

What you’re experiencing is a known behavior with the SharePoint Online Lists connector Implementation 2.0. When using View Mode = All, the connector in Power BI Service refresh currently respects the Default View set in SharePoint rather than consistently pulling all items. That explains why Desktop shows all 651 records, but after a Service refresh only the 49 records from your filtered default view appear.

• Implementation 1.0 does not have this issue, which is why results remain consistent there.

• The product team is aware of this limitation in 2.0 and tracking a fix, though no public ETA has been shared yet.

Workarounds until the fix is available:

• Set the All Items view as the Default view in SharePoint before connecting.

• Use the Web connector with the SharePoint REST API to bypass the view dependency.

• Continue with Implementation 1.0 if you need guaranteed consistency across Desktop and Service refreshes.