Power BI Service Refresh Failure Related to SharePoint Query Folding

Hi Aguila,

Your diagnosis picked up a second data point this morning. shibinkv posted with the same signature: SharePoint source, error code 10224, column wasn't found naming an internal field name, Desktop refreshing fine and the Service failing. Theirs broke around 16 August, yours on the 13th, and neither of you changed anything.

Two unrelated tenants inside a week is worth more than one, so if you do open a support case it's worth saying so in it. It also means Table.StopFolding is the right call rather than something you're stuck with permanently.

One thing worth adding for anyone who finds this later. The reason it looks so much like a renamed column is that the connector shows you the display name while the folded query resolves the internal one, so the error names a field nobody thinks they've touched.

Hi Aguila,

Thanks for the detailed investigation and for sharing your findings. Based on your testing, the issue appears to be isolated to query folding with the SharePoint Online connector in Power BI Service, while the underlying SharePoint data and metadata are accessible successfully.

Using Table.StopFolding or Table.Buffer is a valid workaround based on your testing. Since the model refreshes successfully in Power BI Desktop and disabling folding resolves the Service refresh failure, this may warrant further investigation as a Service/connector-side issue.

Thank you.

Hi Aguila​,

That is a useful isolation, especially since the same model still refreshes in Desktop and the Service succeeds as soon as folding is disabled.

One small recommendation on the workaround: if your only goal is to prevent downstream query folding, I would prefer Table.StopFolding over Table.Buffer. Microsoft specifically recommends Table.StopFolding for that case, since Table.Buffer also materializes data in memory and can add unnecessary overhead.

There is also some precedent for Desktop and Service not behaving identically during connector changes. Microsoft's SharePoint Online List connector documentation notes that capabilities can differ between Power Query hosts because of deployment schedules and host-specific capabilities. I wouldn't take that as proof of a Service regression here, but it does make the Desktop/Service difference worth including in a support case.

If you do escalate this, I would include:

• whether the query uses SharePoint connector implementation 1.0 or 2.0
• the affected column's display name and SharePoint internal name
• the exact transformation after which folding triggers the failure
• workspace region
• refresh/request IDs and timestamps
• confirmation that Table.StopFolding makes the same Service refresh succeed

As an additional diagnostic, testing a duplicate query with the alternate SharePoint connector implementation could help isolate whether the issue is specific to one connector path. I wouldn't change the production model on that basis though, since Microsoft notes that the 2.0 implementation isn't backward compatible with 1.0.

Given the testing you've already done, I agree that this looks much more like something in the folded SharePoint request path than a missing-column issue in the model itself.

Hey PauReis​, Thanks for your response.
Found the solution now. Initially the MultilineFlag column removed in PowerQuery. And i have added it back in the report and published. Now auto refresh also working with this.