You identify the exact record that needs attention in Power BI, but you still cannot act on it from the report. Instead, you have to open SharePoint, Dataverse, or another system, search for the same record again, make the update there, and then return to Power BI to continue working. When this happens repeatedly, even a simple status change or comment turns into unnecessary back-and-forth.
While working on Power Platform implementations at Code Creators, we often see this gap in processes where Power BI already gives users the right information, but the next action still sits outside the report. The issue is not usually a lack of reporting. It is the disconnect between seeing what needs to be done and having a practical way to do it from the same place.
With Power Apps Power BI integration, you can place a canvas app inside a Power BI report and pass selected report data into it. You can then update a record, submit information, add a comment, or complete another business action without leaving the report. In this article, you will learn how to add Power Apps to Power BI, connect report data to the app, handle updates correctly, and avoid the setup issues that commonly affect the integration.
How Power Apps Power BI Integration Works
The integration starts with the Power Apps visual in Power BI.
You add the visual to your report and then assign the fields that your app needs. Power BI passes those fields into the embedded canvas app through the PowerBIIntegration.Data object.
This means your Power App can work with the same record context that you are already viewing in Power BI.
In many Power BI setups, users narrow a report to a specific customer, project, request, or asset before taking action. The embedded app can receive that same filtered context, so they do not have to search for the record again.
However, there is one important distinction you need to understand.
PowerBIIntegration.Data gives the app access to report data, but it does not let the app directly edit the Power BI dataset. If you want users to make changes, your Power App needs a connection to the actual data source, such as SharePoint, Dataverse, or SQL Server.
In simple terms, Power BI tells the app which record you are looking at, while Power Apps updates the system where that record actually lives.
What You Need Before You Add Power Apps to Power BI
Before you build the integration, make sure your Power BI report already contains the fields that the app will need.
You should also have access to a Power Apps environment where you can create or edit a canvas app. If the app will update business data, you also need permission to connect to that source.
It helps to decide the exact action you want users to complete before you start.
In the Power Platform implementations we work with, the embedded app often handles focused actions such as updating a request status, adding a comment, assigning an owner, or submitting approval details. Once that action is clear, you can decide which Power BI fields need to pass into the app.
You should also plan how updated data will appear back in Power BI. If your report uses imported data, Power Apps may save a change to the source immediately while Power BI continues to show the older value until the dataset refreshes.
That refresh behavior matters because otherwise you may think the app failed even though the source record updated correctly.
How to Integrate Power Apps with Power BI
1. Add the Power Apps Visual to Your Report
Start by opening the Power BI report where you want users to take action.
Add the Power Apps visual to the report page and place it close to the visual that drives the action. When a report page includes a request table, placing the Power App close to it usually makes the connection between the record and the available action much clearer for users.
Next, add the fields your app needs to the Power Apps visual.
Approval-focused integrations commonly pass fields such as Request ID, Requestor, Status, and Owner because those values give the app enough context to identify and work with the correct record.
Whenever possible, include a unique record ID.
This is one of the most important parts of a reliable integration. Names, titles, and descriptions can repeat, but a unique ID gives your app a dependable way to find the exact source record that the user wants to update.
2. Create a New Power App or Connect an Existing One
Once you add the required fields, the Power Apps visual gives you the option to create a new app or connect an existing canvas app.
If the app exists mainly to support that Power BI report, creating it from the visual usually gives you the cleanest setup because the Power BI integration is already part of the app.
If you already have a canvas app that performs the required action, you can connect that app instead.
However, be careful when you change the Power BI fields later. If you add or remove fields from the Power Apps visual, open the app for editing through the Power BI service so the updated field configuration reaches Power Apps correctly.
3. Use PowerBIIntegration.Data Inside Power Apps
After the app opens in Power Apps Studio, you can access the report data through:
PowerBIIntegration.Data
For example, if you want to display the Power BI records in a gallery, you can use:
PowerBIIntegration.Data
as the gallery’s Items property.
If your app should work with only one record at a time, you can also use:
First(PowerBIIntegration.Data)
In many cases, however, it is better to pass only the record ID from Power BI and then use that ID to retrieve the complete record from the app’s connected data source.
This keeps the Power BI side simpler and gives your app access to any additional fields it needs without forcing you to send every field through the report.
4. Connect the App to the Data Source You Want to Update
At this point, you need to connect the canvas app to the actual source that stores the record.
Where Power BI reads its records from a SharePoint list, the Power App typically connects to that same list so it can update the source record directly. If your records live in Dataverse, connect the app to the relevant Dataverse table.
Then use the unique ID from PowerBIIntegration.Data to locate the correct source record.
Once the app has the right record, you can use an Edit Form, SubmitForm(), or Patch() to save the changes.
This is the key idea behind Power Apps integration with Power BI: Power BI gives your app the context, while Power Apps handles the update against the underlying business system.
5. Test the Integration with Real Report Filters
Do not test the app only with one record.
Change slicers, filters, and report selections and confirm that the app continues to receive the correct context.
A common testing issue is that the app continues showing the previous record after the report context changes. Test this by moving between different records and confirming that the app refreshes to the correct one each time.
You should also confirm that the update reaches the source system correctly.
If the source shows the new value but Power BI still shows the previous one, check the report’s refresh setup before changing the app logic.
A successful Power Apps update does not always mean the Power BI report will refresh instantly.
6. Publish and Share the App Correctly
Once the integration works, save and publish the canvas app and then publish the Power BI report.
This is also where many otherwise correct integrations fail.
Sharing the Power BI report does not automatically give users access to the Power App.
You need to share the canvas app separately with the people who will use it. Those users also need the required permissions for the data source connected to the app.
This is why the integration may work perfectly for you but fail when another user opens the same report.
If someone can see the Power BI report but cannot use the embedded app, check the app-sharing settings and source permissions before assuming the integration itself is broken.
Keep the Power App Focused on the Action
You will get better results if the embedded app handles one clear task instead of trying to become a full business application inside Power BI.
In practice, the strongest embedded-app scenarios keep the action closely tied to what the report already surfaces. Reports that flag overdue requests often pair well with status updates or comments, while project-risk views commonly need actions such as assigning an owner or setting a due date.
This keeps the experience simple.
Power BI should help you identify what needs attention. Power Apps should help you act on it.
You should also avoid sending more report data to the app than you need. The PowerBIIntegration object has limits on the number of records it can pass, so use Power BI filters to narrow the context and let Power Apps query the source directly when it needs more information.
Common Power Apps and Power BI Integration Problems
If the app loads the wrong record, first check the field you are using to match Power BI data with the source system. A unique ID is much safer than relying on a name, title, or other value that can repeat.
If the app works for you but not for other users, check whether you shared the canvas app separately and whether those users have access to the underlying data source.
If the app saves a change but Power BI still shows the previous value, check how the report gets its data and when that data refreshes. The source can update successfully even when the report has not refreshed yet.
You may also run into problems after changing the fields assigned to the Power Apps visual. In that case, reopen the app for editing from the Power BI service so the updated field configuration can flow into Power Apps correctly.
These checks usually help you separate a real integration problem from a permissions, record-matching, or refresh issue.
How Code Creators Helps with Power Apps and Power BI Integration
A reliable Power Apps and Power BI setup depends on more than placing a Power Apps visual inside a report. The app needs the right report context, a dependable way to identify source records, correct permissions, and a clear refresh strategy so users understand when their changes will appear in Power BI.
At Code Creators, our work with Microsoft Power Platform environments involves connecting these pieces around the way teams actually use their reports and business data. That can include structuring the Power BI fields passed to the app, connecting Power Apps to SharePoint or Dataverse, setting up record-level actions, and resolving permission or refresh issues that can disrupt the user experience.
If you want to make it easier for users to move from insight to action without leaving Power BI, connect with us to build a Power Apps and Power BI integration that fits your existing reporting and business processes.
Conclusion
Power Apps Power BI integration works best when you keep the responsibility of each platform clear. Power BI should identify the record, issue, or action that needs your attention, while Power Apps should handle the update against the underlying data source.
The Power Apps visual passes report context through PowerBIIntegration.Data, and your canvas app uses that context to find the correct source record. From there, you can let users update information, submit details, or complete another business action without leaving the report.
For a reliable setup, pass only the fields the app needs, include a unique record ID, connect Power Apps directly to the source you want to update, and plan how Power BI will reflect those changes after a refresh. You also need to manage Power BI access, Power Apps sharing, and data-source permissions separately.
When you set up those pieces correctly, you remove the unnecessary step of leaving Power BI just to act on the information already in front of you.
Ready to make your Power BI reports more actionable with Power Apps? Book a consultation with us to discuss an integration approach that fits your reporting setup, data sources, and user workflows.
