Fabric Data Flow Gen2 - Missing content from one SPO list column

[cka1ser]

Hi all!

I have an issue with a Data Flow Gen2 that I have been unable to solve...

In an existing data flow gen 2 that imports a SPO list to a warehouse, one column is not imported correctly anymore.

- It is a single line of text column

- It was importing in the past without issues

- Neither the flow nor the sharepoint list did change

- The column shows up in the flow, but is (more or less) empty. More or less means: of about 1200 different entries that are present on sharepoint only one entry is shown. all other rows are empty

- When I create a new data flow gen2, it shows the same behaviour. All columns are imported correctly, only the problem column is not.

Any hints from the community? I have not been able to find similar cases online.

Cheers, Chris 

[tayloramy]

Hi @cka1ser, 

Is this a standard text column, or is it a managed metadata column? 
I've seen this sort of thing with managed taxonomy columns in the past. 

Can you also let us know whgich connector you're using (SharePoint Files, SharePoint List, SharePoint Online List) and what version (The SharePoint Online List connector allows you to select v1 or v2 which behave differently) 

[cka1ser]

Hi! It is the SharePoint Online List connector, v2 and a standard text column. v1 can not be selected. Ends up in an error telling me SharePoint does not support it.

[v-kpoloju-msft · Accepted solution]

Hi @cka1ser, 

Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to @tayloramy, for those inputs on this thread.

Since you are using the SharePoint Online List connector (v2) and the issue persists even in a new Dataflow, this is likely not a transformation issue but a connector/API limitation affecting that specific column. Even standard text columns can return mostly blank values if there’s an internal schema mismatch in SharePoint (e.g., renamed/recreated column or internal name differing from display name). Also, the error with v1 (“SharePoint does not support it”) indicates your tenant does not allow the legacy API, so fallback isn’t possible.

To fix this, first check the column’s internal name in SharePoint List Settings and reselect/re-expand it in Power Query to refresh schema binding. If that does not work, use an OData feed (_api/web/lists/getbytitle('ListName')/items) instead of the connector this is the most reliable workaround and often returns the correct values. As a quick test, create a new text column and copy some values; if it works, the original column likely has an internal inconsistency.

Hope that clarifies. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.

[v-kpoloju-msft]

Hi @cka1ser, 

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

[v-kpoloju-msft]

Hi @cka1ser, 

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.