Getting Row count but column headers not showing in power apps

(1) Share

Report

Posted on by AS-16011928-0

Hi All,

I am trying to integrate Power Apps into Power BI using the standard approach, but I’m facing an issue while passing selected row data. My setup and problem are as follows:

I have added the Power Apps visual to a Power BI report.
I added the required column names from the dataset into the Power Apps visual.
I either created a new app or selected an existing app from the Power Apps visual.
In the Power BI report, I have a table visual, and I select a single row from that table.
Inside Power Apps:
- I use CountRows(PowerBIIntegration.Data) and it correctly returns 1 when a single row is selected.
- I also use JSON(First(PowerBIIntegration.Data), JSONFormat.Compact) to convert the selected row into a string so I can visualize the data.
However, after publishing the report and selecting a row in the table visual:
- The row count in Power Apps correctly shows 1
- But the JSON output in the text label is coming as a blank JSON object {}

My question is:

Why does PowerBIIntegration.Data show 1 row but return an empty JSON object {} for the selected record?
What conditions or configurations could cause Power Apps to receive the row context without any column data?
Are there any known limitations related to storage mode (Import vs DirectQuery), relationships, or Power Apps visual schema caching that could lead to this behavior?
My storage Mode is Import

Any insights or suggestions would be greatly appreciated.

Thanks in advance!

Screenshot 2026-0...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

lbendlin 8,716 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

PowerBIIntegration.Data returns a table. Whatever columns you added to the PowerApps visual will be handed over to PowerApps through that integration (observing the current filter context which impacts the row count).

Confirm that the PowerApps visual has columns assigned.

Confirm that the PowerApps visual is impacted by the same filters as your table visual.

Was this reply helpful? Yes No
Suggested answer

BriannaReddick 25 on at

Like
a
(1)

Report
Copy link

Link copied!

This should not be a data issue unless you are running into a filter context issue - are the exact same columns in your table visual and in the power app component?

They do not need to match but you do want to make sure having 1 record selected filters the power app as you would expect. My go to troubleshooting method is to duplicate the page and switch your power app component back into a table on the other page. When you click to cross filter make sure the table that is the datasource for the power app is filtering as expected.

If that is working as you intend then you are actually running into an fx issue. I would through a gallery in your power app and set the items to PowerBIIntegration.Data and see how the data loads.

I do see you are using a variable in your screenshots - When building an app off of the bi integration you don't want to store the data in a collection or set a variable on load - just reference the datasource directly in your formulas. The app will perform as you want, since the data source limits the data ingested anyway, you don't really need the collections collections and variables will prevent the dynamic filtering you are wanting.

1 people found this reply helpful.

Was this reply helpful? Yes No
AS-16011928-0 29 on at

Like
a
(0)

Report
Copy link

Link copied!
Here’s a cleaned-up, professional, and community-friendly version of your response. I’ve kept the tone polite, clear, and concise while improving structure and readability:

Hi @Brianna,

Thank you for your response.

Yes, the columns are the same in both the table visual and the Power Apps visual.

I tried duplicating the page. When I click a row in the table:

On the same page, the table correctly filters the Power Apps visual (I temporarily converted the Power Apps visual into a table to validate this).

On the duplicated page, the selected row is not reflected, which I believe is expected behavior in Power BI, as cross-page filtering does not persist.

I also tested using a Gallery control in Power Apps. When I set the Items property to PowerBIIntegration.Data, I do not see any column names in IntelliSense. The columns are not available for selection, which suggests that the schema is not being recognized in Power Apps.

Regarding the fx issue, I need to read more about it, as I am fairly new to Power Apps and the Power Platform ecosystem.

Please check below Attachment.

Screenshot 2026-0...
Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

1 people found this reply helpful.

Was this reply helpful? Yes No
AS-16011928-0 29 on at

Like
a
(0)

Report
Copy link

Link copied!

HI Brianna,

As fx is a function language similar to other microsoft tools such as Microsoft EXcel, power BI. I don't see any issue with formula as. I am using POwerBIIntegartion.Data. (I am not getting any column names here) in intellisense.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Power Platform 1919 2,254 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, does your dataset contain any date-type fields? If so, you may encounter errors when converting the data into a JSON object.

as you can see, my due date column is date datetype ,

this will cause issue and return blank object ({}).

You can try using a text column (convert date to text) and see the JSON object , it should work.

Was this reply helpful? Yes No
Suggested answer

Pstork1 69,556 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

You need to use ParseJSON() not JSON() to get the fields from the PowerBIintegration object. The Data property of that object is already presented as an array/collection. JSON() will convert the array back into a string. If you want to extract records from the first field then you need to use ParseJSON() and cast the fields to the appropriate data types.

ParseJSON function - Power Platform | Microsoft Learn

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!

Paul Papanek Stork, MVP
Blog: https://www.dontpapanic.com/blog

Was this reply helpful? Yes No