Forum Discussion
Power Apps Visual in Power Bi Report in Power BI Service
Hi Team,
I have a Power BI report having date from calender table, name from Article Table and 2 measures along with many other measures and dimensions. In the report, in a table visual, I have included Date, Article name, and two measures. I have used Power Apps visual in which Date, Article name and those two measures were given as parameters. In Power apps, I have a entity attached as a data source which is used for the form. The item property of the form is
LookUp(EntityName,PrimaryName=First(PowerBIIntegration.Data).fieldfromreport)
Now, It is able to show me the first record in the Power apps Visual, but on selection of any other record, It is not changing.
Can anyone solve my issue? Is it a good idea to take parameters from different entities in Power Bi Report to Power Apps? In videos and tutorials, I have seen people using parameters from one entity and with no measures. Please Help !!
Hi Anonymous ,
The following limitations apply to the Power Apps visual:
- The maximum number of records that can be passed from Power BI to Power Apps visual using "PowerBIIntegration" object is limited to 1000.
- Power Apps visual is only supported for guest users when the following conditions are met:
- The canvas app URI (weblink) includes the tenantId of the app in the query string.
- The Power BI portal authenticates the user, instead of allowing anonymous access.
- The canvas app is shared with the guest user attempting to see the contents of the app.
- Power Apps visual doesn't support multi-level embedding of Power Apps in Sovereign clouds. For example, embedding a Power BI report with Power Apps visual to a SharePoint page, or further embedding that SharePoint page to a Teams channel isn't supported on sovereign clouds.
- If you change the data fields associated with the visual, you must edit the app from within the Power BI service by selecting the ellipsis (...) and then selecting Edit. Otherwise, the changes won't be propagated to Power Apps, and the app will behave in unexpected ways.
- The Power Apps visual can't trigger a refresh of Power BI reports and Power BI data sources from within Power BI Desktop. If you write back data from the app to the same data source as the report, your changes won't be reflected immediately in Power BI Desktop. Changes are reflected on the next scheduled refresh.
- The Power Apps visual can't filter the data or send any data back to the report.
- You'll need to share the Power Apps app separately from your report. Learn about sharing apps in Power Apps.
- Power BI Report Server doesn't support the Power Apps visual.
- Following limitations apply when using the
PowerBIIntegration.Refresh()function:- You must create a new app from Power Apps visual in Power BI report for this function to be available in the app.
- You must use a source that supports DirectQuery and the data connection must be created using DirectQuery method.
- Power Apps in Power BI Desktop provides data to Power Apps Studio when creating apps but not while editing. Use Power BI Web to preview the data while editing apps.
- The Power BI mobile app doesn't support microphone control in Power Apps visuals.
For more information, please refer to:Power Apps visual for Power BI - Power Apps | Microsoft Docs
Best regards,
Yadong Fang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
v-yadongf-msftCommunity Support
Hi Anonymous ,
The following limitations apply to the Power Apps visual:
- The maximum number of records that can be passed from Power BI to Power Apps visual using "PowerBIIntegration" object is limited to 1000.
- Power Apps visual is only supported for guest users when the following conditions are met:
- The canvas app URI (weblink) includes the tenantId of the app in the query string.
- The Power BI portal authenticates the user, instead of allowing anonymous access.
- The canvas app is shared with the guest user attempting to see the contents of the app.
- Power Apps visual doesn't support multi-level embedding of Power Apps in Sovereign clouds. For example, embedding a Power BI report with Power Apps visual to a SharePoint page, or further embedding that SharePoint page to a Teams channel isn't supported on sovereign clouds.
- If you change the data fields associated with the visual, you must edit the app from within the Power BI service by selecting the ellipsis (...) and then selecting Edit. Otherwise, the changes won't be propagated to Power Apps, and the app will behave in unexpected ways.
- The Power Apps visual can't trigger a refresh of Power BI reports and Power BI data sources from within Power BI Desktop. If you write back data from the app to the same data source as the report, your changes won't be reflected immediately in Power BI Desktop. Changes are reflected on the next scheduled refresh.
- The Power Apps visual can't filter the data or send any data back to the report.
- You'll need to share the Power Apps app separately from your report. Learn about sharing apps in Power Apps.
- Power BI Report Server doesn't support the Power Apps visual.
- Following limitations apply when using the
PowerBIIntegration.Refresh()function:- You must create a new app from Power Apps visual in Power BI report for this function to be available in the app.
- You must use a source that supports DirectQuery and the data connection must be created using DirectQuery method.
- Power Apps in Power BI Desktop provides data to Power Apps Studio when creating apps but not while editing. Use Power BI Web to preview the data while editing apps.
- The Power BI mobile app doesn't support microphone control in Power Apps visuals.
For more information, please refer to:Power Apps visual for Power BI - Power Apps | Microsoft Docs
Best regards,
Yadong Fang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi v-yadongf-msft ,
Thank you for the explanation. For the time being, I am bound to use this method knowing all the limitations. But I really appreciate the explanation. Thank you so much.