That symptom (rows counted but the column headers blank) almost always means the data is arriving fine, but the column names coming back aren't what the control is binding to. A few things to check, roughly in order:
Look at the actual field names in the result. Drop a temporary label set to something like First(YourData).SomeField, or check your flow/query output. If you're pulling from Power BI's "run a query against a dataset" action, the columns usually come back prefixed and bracketed, like Table[Column], not a clean Column. That's exactly why the row count works but ThisItem.Column shows nothing: the real field name isn't what you typed.
Clean up the field names before they reach the control. Easiest is to reshape in the flow with a Select action so each row has plain keys (Column instead of Table[Column]). If you'd rather do it in the app, rebuild the data with RenameColumns, AddColumns, or ShowColumns into a collection with clean names and bind the gallery to that.
If the data is untyped (for example from ParseJSON), Power Apps won't auto-detect columns at all. You have to cast each field explicitly with Value(), Text(), and so on, and define the columns yourself.
For the classic Data Table control specifically, it only auto-fills the Fields pane from a typed source. If your Items is dynamic, add the fields manually in the Fields pane, or switch to a Gallery or the modern Table control, which give you direct control over each column's binding.
If you can share the exact source (a Power BI dataset query versus a flow returning the data) and a screenshot of the field names on one returned record, it's usually quick to pin down which of these it is. Hope that helps.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.