Forum Discussion

RGonz1215's avatar
RGonz1215
Regular Visitor
4 months ago
Solved

PBI Desktop and SharePoint List Refresh Error

Thank you for reading my post and helping solve this issue. There are other related threads however I could not find any that address my particular issue. My report uses two different SharePoint l...
Need Help
  • RGonz1215's avatar
    RGonz1215
    4 months ago

    Good morning. Yes I have it working now. These are the steps used for the solution.

    Key Recommendations:

     

    1. We indexed the vast majority of columns in a custom view. 

     

    2. Using implementation 2.0 we did not have the option to select a specific view. We could only select 'All Columns' or 'Default View'. Regardless of what we selected as the default, it would not work. So we went with implementation 1.0 and it synced.

     

    3. Upon connecting to the data source we deleted all unncessary columns in the third step. 1st - Source, 2nd - Navigation, 3rd - Remove Columns. This helped greatly reduce loading times and obtain the data.

    We verified all permissions were correct and expanded the cache memory to the highest it could go. Not sure what help those things did but we were kind of throwing spaghetti at the wall.

     
v-anbandari's avatar
v-anbandari
Community Support
4 months ago

Hi RGonz1215  ,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to the Zanqueta for sharing valuable insights.
 

Could you please confirm if your issue has been resolved using the suggested approach? This will help other community members facing similar scenarios.
 

Thank you for being part of the Microsoft Fabric Community.

RGonz1215's avatar
RGonz1215
Regular Visitor
4 months ago

Good morning. Ok, sorry about the delay. Thank you again everyone for sticking with us as we try and figure this out.

We took the following steps:

  1. created a custom view within the sharepoint list just for this report
  2. indexed the majority of the columns within this view
  3. made the new custom view the default
  4. started a new power bi report to test
  5. went with 2.0 and default
  6. received the same error code

We also tried:

  1. connecting to the SP list as we have been
  2. preview loaded in PBI report
  3. 1st step we removed all unneccessary columns
  4. received the same error code

So we attempted:

  1. exporting the view directly to PBI Online through SP
  2. model loaded and then we downloaded the PBIX file to open in PBI Desktop
  3. did not work

I am sure that I am doing something wrong here. We just can't figure it out.

  • RGonz1215's avatar
    RGonz1215
    Regular Visitor
    4 months ago

    So, I'll go ahead and face palm myself. We just got it to sync going with implementation 1.0.

    It did mess up a lot of our columns and we will have do some other fancy magic to get things back but at least it syncs now. We just loaded 5,268 rows.

    • v-anbandari's avatar
      v-anbandari
      Community Support
      4 months ago

      Hi RGonz1215  ,

      Thanks for the update. Could you please confirm if everything is working as expected now, or if you’re still facing any issues?

      Also, let us know if you need any further assistance .

      Thank you.

       

      • RGonz1215's avatar
        RGonz1215
        Regular Visitor
        4 months ago

        Good morning. Yes I have it working now. These are the steps used for the solution.

        Key Recommendations:

         

        1. We indexed the vast majority of columns in a custom view. 

         

        2. Using implementation 2.0 we did not have the option to select a specific view. We could only select 'All Columns' or 'Default View'. Regardless of what we selected as the default, it would not work. So we went with implementation 1.0 and it synced.

         

        3. Upon connecting to the data source we deleted all unncessary columns in the third step. 1st - Source, 2nd - Navigation, 3rd - Remove Columns. This helped greatly reduce loading times and obtain the data.

        We verified all permissions were correct and expanded the cache memory to the highest it could go. Not sure what help those things did but we were kind of throwing spaghetti at the wall.