Forum Discussion
Fabric Data Flow Gen2 - Missing content from one SPO list column
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.
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.
Community SupportHi 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.