Hello! That solution does allow refreshing in the service. My SP list already has 20,000 rows and increases every day; it is refreshed at least 8 times a day directly from the service. The M code in that link deals with that, and it works really well.
About my problem, I was able to fix it! However, I truly don't understand the issue in the first place.
My dataset is connected to 9 simple SharePoint lists (between 20 and 300 rows tops), then 2 more lists (my fact tables) that have 20,000 rows each, and 3 more fact tables with under 1,000 rows. There is 1 more table that comes from an Excel file. Lastly, I combine some PDF files that contain a small table.
Finally, after many tries, I discovered that if I exclude one of the SharePoint lists that contains only 295 rows, 5 text columns, and 1 true/false column, my report refreshes in the Power BI service without a problem. On the other hand, if I include that simple SP list, my report won't refresh in the service due to Resource Governing
"Resource Governing: This operation was canceled because there wasn't enough memory to finish running it. Either reduce the memory footprint of your dataset by doing things such as limiting the amount of imported data, or if using Power BI Premium, increase the memory of the Premium capacity where this dataset is hosted. More details: consumed memory 16,291 MB, memory limit 16,291 MB, database size before command execution 92 MB. See https://go.microsoft.com/fwlink/?linkid=2159753 to learn more."
Honestly, I don't get it.
I have the Pro license. I get that it has limitations, but my datasets are rather small, and how can a 295-row list affect the refresh process only on the service but not in Power BI Desktop?
I tried to include that 295-row SP list using V1 connector, V2, and even the M code I previously shared (the one I use with my biggest lists), and any time that SP list is included in the dataset, it won't complete the refresh process.
