Merge pull request #3208 from MicrosoftDocs/matp-1953441

Revised per 1953441

Author: Mattp123

powerapps-docs/maker/model-driven-apps/embed-powerbi-report-in-system-form.md

@@ -1,8 +1,7 @@
 ---
 title: "Embed a Power BI report in a model-driven system form | MicrosoftDocs"
 ms.custom: ""
-ms.date: 03/05/2019
-ms.reviewer: ""
+ms.date: 08/04/2020
 ms.service: powerapps
 ms.topic: "get-started-article"
 author: "adrianorth"
@@ -28,7 +27,7 @@ This feature requires exporting a solution, modifying it to add the xml snippet,
 You can use your Power BI reports and tiles by simply embedding them, and get the exact same report. This does not involve contextualizing them to the current model-driven form, and hence you get the same report or tile on all records of the entity. For example, the following report shows the geographic ___location of all accounts at once, and is useful to show summary information.
 
 > [!div class="mx-imgBorder"] 
-> ![](media/embed-powerbi/embed-powerbi-report-in-system-form-unfiltered.png "Embed-powerbi-report-in-system-form-unfiltered")
+> ![Embeded  Power BI report without contextual filtering](media/embed-powerbi/embed-powerbi-report-in-system-form-unfiltered.png "Embeded  Power BI report without contextual filtering")
 
 You can embed a section that hosts Power BI reports and tiles in your system forms by adding the following code snippet inside the `<sections>` block of the form XML. Then, import the solution in the target environment. 
 
@@ -71,7 +70,7 @@ You can embed a section that hosts Power BI reports and tiles in your system for
 You can make the Power BI reports and tiles more meaningful by applying contextual filters to the current model-driven form, so that the report or tile is filtered based on attributes of the current record. For example, the following report shows the geographic ___location of an account, by filtering the Power BI report using the account name. This allows a single report to show contextualized information for all records of the entity.
 
 > [!div class="mx-imgBorder"] 
-> ![](media/embed-powerbi/embed-powerbi-report-in-system-form-filtered.png "Embed-powerbi-report-in-system-form-filtered")
+> ![Embeded Power BI report with contextual filtering](media/embed-powerbi/embed-powerbi-report-in-system-form-filtered.png "Embeded Power BI report with contextual filtering")
 
 The filtering is done by adding a `<PowerBIFilter>` element in the `<parameter>` block as shown here. You can use any attribute of the form's entity to construct the filter expression. More information: [Constructing Filters](https://github.com/Microsoft/PowerBI-JavaScript/wiki/Filters#contructingfilters) to understand how to create your own filters.
 
@@ -117,24 +116,46 @@ The target part of the previous expression identifies the table and the column t
 
 You can create more complex filter expressions by looking at examples from [Constructing Filters](https://github.com/Microsoft/PowerBI-JavaScript/wiki/Filters#contructingfilters) and providing the appropriate values for $schema and filterType. Be sure to escape every literal in the filter part using *\"*, so that the JSON is generated correctly.
 
+## Remove unmodified attribute before import
+Before you import the solution into the target environment, make sure the unmodified attribute isn’t included in formXml section of the customizations.xml file. If the unmodified attribute is present in the XML that includes the Power BI control XML, remove the attribute before you import the solution into the target environment. For example, replace `<systemform unmodified="1">` with `<systemform>`.
+
+Additionally, when you export the solution as managed, add the **solutionaction="Added"** attribute to the formXml as indicated in the **cell** element below: 
+
+```xml
+<cell id="{7d18b61c-c588-136c-aee7-03e5e74a09a1}" showlabel="true" rowspan="20" colspan="1" auto="false" solutionaction="Added">
+  <labels>
+    <label languagecode="1033" description="Accounts (Parent Account)"/> 
+  </labels> 
+  <control id="unfilteredreport" classid="{8C54228C-1B25-4909-A12A-F2B968BB0D62}">
+    <parameters>
+      <PowerBIGroupId>00000000-0000-0000-0000-000000000000</PowerBIGroupId>
+      <PowerBIReportId>544c4162-6773-4944-900c-abfd075f6081</PowerBIReportId>      
+      <TileUrl>https://xyz.powerbi.com/reportEmbed?reportId=544c4162-6773-4944-900c-abfd075f6081</TileUrl>        
+     </parameters> 
+  </control> 
+</cell>
+```
+
+
+
 ## Known issues and limitations
-1. This integration is available only in the Unified Interface client, on supported web browsers and mobile devices.
-2. Opening this form in the Power Apps form designer will not show the control in a meaningful way. This is because the control is customized outside of the form designer.
-3. Users will be authenticated into Power BI automatically with their Power Apps username and password. If a Power BI account with matching credentials doesn’t exist, a sign in prompt is displayed as illustrated here. 
+- This integration is available only in the Unified Interface client, on supported web browsers and mobile devices.
+- Opening this form in the Power Apps form designer will not show the control in a meaningful way. This is because the control is customized outside of the form designer.
+- Users will be authenticated into Power BI automatically with their Power Apps username and password. If a Power BI account with matching credentials doesn’t exist, a sign in prompt is displayed as illustrated here. 
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-1.png "Embed-powerbi-report-in-system-form-auth-1")
+   > ![Power BI sign in prompt](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-1.png "Power BI sign in prompt")
 
-4. No data will display if an incorrect account is used to log into Power BI. To sign in with the correct credentials, sign out, and then sign in again.
+    No data will display if an incorrect account is used to log into Power BI. To sign in with the correct credentials, sign out, and then sign in again.
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-2.png "Embed-powerbi-report-in-system-form-auth-2")
+   > ![Sign in to Power BI service](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-2.png "Sign in to Power BI service")
 
    > [!div class="mx-imgBorder"] 
-   > ![](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-3.png "Embed-powerbi-report-in-system-form-auth-3")
+   > ![User that is signed in doesn't have appropriate permission](media/embed-powerbi/embed-powerbi-report-in-system-form-auth-3.png "User that is signed in doesn't have appropriate permission")
 
-5. The view of the report data shown inside Power Apps is the same as that in Power BI, and Power Apps security roles and privileges don't affect the data that is displayed. Hence, the data is essentially the same as what the creator of the Power BI dataset would see. To apply data access restrictions similar to Power Apps security roles and teams, use [Row-level security (RLS) with Power BI](https://docs.microsoft.com/power-bi/service-admin-rls).
-6. If the form doesn’t show the Power BI report after importing the solution and publishing customizations, open it in the model-driven form editor and save it, so that the form JSON is regenerated.
+- The view of the report data shown inside Power Apps is the same as that in Power BI, and Power Apps security roles and privileges don't affect the data that is displayed. Hence, the data is essentially the same as what the creator of the Power BI dataset would see. To apply data access restrictions similar to Power Apps security roles and teams, use [Row-level security (RLS) with Power BI](https://docs.microsoft.com/power-bi/service-admin-rls).
+- If the form doesn’t show the Power BI report after importing the solution and publishing customizations, open it in the model-driven form editor and save it, so that the form JSON is regenerated.
 
 
 ### See also