Live publish

Author: buck1ey

powerapps-docs/maker/canvas-apps/controls/control-power-bi-tile.md

@@ -6,7 +6,7 @@ ms.service: powerapps
 ms.topic: reference
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 08/30/2021
+ms.date: 02/02/2022
 ms.subservice: canvas-maker
 ms.author: chmoncay
 search.audienceType: 
@@ -16,6 +16,7 @@ search.app:
 contributors:
   - tapanm-msft
   - chmoncay
+  - miglisic
 ---
 # Power BI tile control in Power Apps
 
@@ -28,7 +29,8 @@ Don't have Power BI? [Sign up](/power-bi/service-self-service-signup-for-power-b
 Take advantage of your existing data analysis and reporting by displaying your **[Power BI tiles](/power-bi/service-dashboard-tiles)** inside your apps. Specify the tile that you want to show by setting its **Workspace**, **Dashboard**, and **Tile** properties in the **Data** tab of the options panel.
 
 > [!NOTE]
-> - Power BI tile control isn't availbale on [GCC High and DoD](/power-platform/admin/powerapps-us-government#power-apps-us-government-service-urls) environments.
+> - Power BI tile control isn't available on [GCC High and DoD](/power-platform/admin/powerapps-us-government#power-apps-us-government-service-urls) environments.
+> - Power BI tile control isn't available in China.
 > - For licensing requirements when embedding Power BI tile, see [Licensing](/power-bi/collaborate-share/service-embed-secure#licensing).
 
 ## Sharing and security

powerapps-docs/maker/canvas-apps/mixed-reality-overview.md

@@ -6,7 +6,7 @@ ms.service: powerapps
 ms.topic: overview
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 3/25/2021
+ms.date: 02/02/2022
 ms.subservice: canvas-maker
 ms.author: anuitz
 search.audienceType: 
@@ -83,5 +83,8 @@ Start installing the controls in your apps:
 - Measure distance, area, and volume with the **[Measure in mixed reality](mixed-reality-component-measure-distance.md)** control.
 - Create and view predefined 3D shapes with the **[View shape in mixed reality](mixed-reality-component-view-shape.md)** control.
 
+### See also
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[Microsoft Learn: Build a 3D mobile app with Power Apps in mixed reality](/learn/modules/power-apps-tutorial/)
+
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/model-driven-apps/accessibility-app-designer-site-map-designer-my-apps-page.md

@@ -100,7 +100,6 @@ This article itemizes the keyboard shortcuts for Power Apps.
 
 |Browser|Jaws|Narrator|Voice Over|  
 |-------------|----------|--------------|----------------|  
-|Internet Explorer 11|Yes|Yes|No|  
 |Google Chrome|Yes|No|No|  
 |Firefox|Yes|No|No|  
 |Safari|No|No|Yes|  

powerapps-docs/maker/model-driven-apps/design-performant-forms.md

@@ -71,7 +71,7 @@ The `openForm` client API method allows a parameter option to display a form in
 
 Using the most up-to-date web browser is key to ensuring your model-driven app runs as fast as possible.  The reason for this is that many of the performance improvements can only be used in the newer modern browsers.
 
-For example, if your organization has older versions of Firefox, non-Chromium-based browsers, and so on, many of the performance gains that are built into a model-driven app will not be available in the older browser versions because they don't support features that the app depends on to run quickly and smoothly. And if you're using Internet Explorer, it's no longer supported.
+For example, if your organization has older versions of Firefox, non-Chromium-based browsers, and so on, many of the performance gains that are built into a model-driven app will not be available in the older browser versions because they don't support features that the app depends on to run quickly and smoothly.
 
 In most cases, you can expect to see page load improvements by just switching to Microsoft Edge, updating to the latest current browser version from an older version, or moving to a modern Chromium-based browser.
 

powerapps-docs/maker/model-driven-apps/form-component-control.md

@@ -112,7 +112,7 @@ Note the following limitations when you add the form component control to a tabl
 
 - Using the same form for different form component controls isn't supported.
 
-- The form that you use with a form component must be included in your app. More information: [Add a component](add-edit-app-components.md#add-a-component).
+- The form that you use with a form component must be included in your app. If it isn't, or if the current user does not have access to the form, it will fallback to the top-most main form that is included in the app and available to the user (based on form order). More information: [Add a component](add-edit-app-components.md#add-a-component).
 
 - You may notice that the timeline wall may not update when a column that is used to set the timeline wall has changed in the form component. When the page is refreshed the timeline wall will update as expected.
 

powerapps-docs/maker/model-driven-apps/model-app-page-issues.md

@@ -63,8 +63,6 @@ The custom page is a new page type within model-driven apps. Custom pages bring
 
 * Native player support is available for iOS and Android in online-only mode. Offline support currently isn't supported. The preview Dynamics 365 Windows player displays a blank page when a custom page is opened.
 
-* When a user running Internet Explorer opens a custom page, an error message will appear indicating Internet Explorer isn't supported.
-
 * While attempting to sign in, the current behavior caused by a user selecting anywhere away from the sign in box causes the pop out window for sign in to shift behind the app browser.
 
 * When a user runs an app that isn't compliant with their organization's [Data Loss Prevention (DLP) policies](/power-platform/admin/wp-data-loss-prevention), they'll see an error dialog and the 'Technical details' reflects the app isn't DLP compliant. 

powerapps-docs/maker/portals/add-form.md

@@ -5,7 +5,7 @@ author: neerajnandwana-msft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 08/24/2021
+ms.date: 02/02/2022
 ms.subservice: portals
 ms.author: nenandw
 ms.reviewer: ndoelman
@@ -66,9 +66,6 @@ To add a form component:
 
     - **Show captcha for anonymous users**: Displays captcha to anonymous users.
 
-    > [!NOTE]
-    > Captcha control is currently limited to only English language for audio, and Latin characters for image.
-
     - **Show captcha for authenticated users**: Displays captcha to authenticated users.
 
     - **Permissions**: Table permissions to be considered for the form. [Configure table permissions](configure/entity-permissions-studio.md) to make the form available to anyone, or any specific roles.

powerapps-docs/maker/portals/component-framework-liquid.md

@@ -5,21 +5,20 @@ author: GitanjaliSingh33msft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 11/10/2021
+ms.date: 02/02/2022
 ms.subservice: portals
 ms.author: gisingh
 ms.reviewer: ndoelman
 contributors:
   - nickdoelman
   - GitanjaliSingh33msft
-  - nickdoelman
 ---
 
-# Liquid template tag for code components (preview)
+# Liquid template tag for code components
 
 [This article is pre-release documentation and is subject to change.]
 
-Power Apps component framework empowers professional developers and app makers to create code components for model-driven and canvas apps. These code components can provide an enhanced experience for users working with data on forms, views, and dashboards. More information: [Use code components in portals (preview)](component-framework.md)
+Power Apps component framework empowers professional developers and app makers to create code components for model-driven and canvas apps. These code components can provide an enhanced experience for users working with data on forms, views, and dashboards. More information: [Use code components in portals](component-framework.md)
 
 > [!IMPORTANT]
 > The Liquid template tag for code components requires portals version [9.3.10.x or later](/power-platform/released-versions/portals/portalupdate9310x).
@@ -50,15 +49,15 @@ You can use the [sample map control](../../developer/component-framework/sample-
 
 ## Tutorial: Use code components on pages with Liquid template tag
 
-In this tutorial, you'll configure Power Apps portals to add the component to a webpage and set access for the **Web Resource** table. You'll then visit the portals webpage and interact with the component.
+In this tutorial, you'll configure Power Apps portals to add the component to a webpage. You'll then visit the portals webpage and interact with the component.
 
 ### Before you begin
 
 If you're using the sample code component used in this tutorial, ensure that you first import the sample solutions to the environment before you begin. To learn about solution import, go to [Import solutions](../data-platform/import-update-export-solutions.md).
 
 ### Prerequisites
 
-For prerequisites, and to learn about supported/unsupported code components in portals, go to [Use code components in portals (preview)](component-framework.md).
+For prerequisites, and to learn about supported/unsupported code components in portals, go to [Use code components in portals](component-framework.md).
 
 > [!NOTE]
 > This tutorial uses a sample code component created using Power Apps component framework to demonstrate a map control on a webpage. You can also use any existing or new component of your own, and any other webpage for this tutorial. In this case, be sure to use your component and webpage when following the steps in this tutorial. For more information about how to create code components, go to [Create your first component](../../developer/component-framework/implementing-controls-using-typescript.md).
@@ -110,10 +109,6 @@ For prerequisites, and to learn about supported/unsupported code components in p
 
 1. The webpage will now show the control added on it.
 
-### Step 2. Allow Read access to the Web Resource table
-
-Follow the steps outlined in [Allow Read access to the Web Resource table](component-framework-tutorial.md#step-5-allow-read-access-to-the-web-resource-table).
-
 ## Next steps
 
 [Overview: Use code components in portals](component-framework.md)
@@ -126,3 +121,5 @@ Follow the steps outlined in [Allow Read access to the Web Resource table](compo
 [Create your first component](../../developer/component-framework/implementing-controls-using-typescript.md) <br>
 [Add code components to a column or table in model-driven apps](../../developer/component-framework/add-custom-controls-to-a-field-or-entity.md)<br>
 [Implement a sample portal Web API component](implement-webapi-component.md)
+
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]

powerapps-docs/maker/portals/component-framework-tutorial.md

@@ -5,7 +5,7 @@ author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 04/21/2021
+ms.date: 02/02/2022
 ms.subservice: portals
 ms.author: nenandw
 ms.reviewer: ndoelman
@@ -15,11 +15,9 @@ contributors:
   - HemantGaur
 ---
 
-# Tutorial: Use code components in portals (preview)
+# Tutorial: Use code components in portals
 
-[This article is pre-release documentation and is subject to change.]
-
-In this tutorial, you'll create a sample component using Power Apps component framework. You'll package this component to a Dataverse environment and add the component to a model-driven app. You'll then configure Power Apps portals to add the component to a basic form, set access for the **Web Resource** table, and add the basic form to a webpage. Finally, you'll visit the portals webpage and interact with the component.
+In this tutorial, you'll create a sample component using Power Apps component framework. You'll package this component to a Dataverse environment and add the component to a model-driven app. You'll then configure Power Apps portals to add the component to a basic form and add the basic form to a webpage. Finally, you'll visit the portals webpage and interact with the component.
 
 ## Prerequisites
 
@@ -52,117 +50,86 @@ In this step, you’ll create a new basic form in portals and then add the compo
 
 1.  Open [Portal Management](configure/configure-portal.md) app.
 
-2.  On the left pane, under **Content**, select **Basic Forms.**
+1.  On the left pane, under **Content**, select **Basic Forms.**
 
-3.  Select **New**.
+1.  Select **New**.
 
-4.  Enter **Name**. For example, *Opportunities basic form with code
+1.  Enter **Name**. For example, *Opportunities basic form with code
     component*.
 
-5.  Select **Basic Name** as *Opportunity*.
+1.  Select **Basic Name** as *Opportunity*.
 
-6.  For **Form Name**, select the model-driven app form that you added the code
+1.  For **Form Name**, select the model-driven app form that you added the code
     component to earlier in this tutorial.
 
-7.  Select the **Tab Name**.
+1.  Select the **Tab Name**.
 
-8.  Select your portal **Website**.
+1.  Select your portal **Website**.
 
     ![Configure basic form using Portal Management app.](media/component-framework/new-entity-form.png "Configure basic form using Portal Management app")
 
-9.  Select **Save & Close**.
+1.  Select **Save & Close**.
 
 ### Step 4.2. Add code component to the basic form
 
 1.  Open [Portal Management](configure/configure-portal.md) app.
 
-2.  On the left pane, under **Content**, select **Basic Forms.**
+1.  On the left pane, under **Content**, select **Basic Forms.**
 
-3.  Select the basic form you created in the previous step.
+1.  Select the basic form you created in the previous step.
 
-4.  Select **Related**.
+1.  Select **Related**.
 
-5.  Select **Basic Form Metadata**.
+1.  Select **Basic Form Metadata**.
 
-6.  Select **New Basic Form Metadata**.
+1.  Select **New Basic Form Metadata**.
 
-7.  Select **Type** as **Attribute**.
+1.  Select **Type** as **Attribute**.
 
-8.  Select **Attribute Logical Name** as *Budget Amount (budgetamount)*.
+1.  Select **Attribute Logical Name** as *Budget Amount (budgetamount)*.
 
     ![Budget Amount attribute logical name.](media/component-framework/attribute-logical-name.png "Budget Amount attribute logical name")
 
-9.  Enter **Label**. For example, *Budget Amount*.
+1.  Enter **Label**. For example, *Budget Amount*.
 
-10. For **Control Style**, select **Code component**.
+1. For **Control Style**, select **Code component**.
 
     ![Control Style.](media/component-framework/control-style.png "Control Style")
 
-11. Select **Save & Close**.
-
-## Step 5. Allow Read access to the Web Resource table
-
-1.  Open [Portal Management](configure/configure-portal.md) app.
-
-2.  On the left pane, under **Security**, select **Table Permissions.**
-
-3.  Select **New**.
-
-4.  Enter **Name**. For example, *Permissions for code component on the Web
-    Resource table*.
-
-5.  Select **Table** as **Web Resource (webresource)**.
-
-6.  Select your **Website**.
-
-7.  For **Scope**, select **Global**.
-
-8.  In the **Privileges** section, select **Read**.
-
-9.  Select **Save.**
-
-    ![Permissions for code component.](media/component-framework/permissions.png "Permissions for code component")
-
-10. Under **Web Roles**, select **Add Existing Web Role**.
-
-11. Choose the web role as required. For example, choose the *Authenticated Users* web role of a portal website record to allow access to all authenticated users.
-
-    ![Web Role for code component.](media/component-framework/webrole.png "Web Role for code component")
-
-12. Select **Save & Close**.
+1. Select **Save & Close**.
 
-## Step 6. Create a webpage in portals with the basic form
+## Step 5. Create a webpage in portals with the basic form
 
 1.  Open your portal in [Power Apps portals Studio](portal-designer-anatomy.md).
 
-2.  On the top-left corner, select **New page**.
+1.  On the top-left corner, select **New page**.
 
-3.  Select **Blank**.
+1.  Select **Blank**.
 
-4.  On the right-side property pane, update the webpage name. For example, *Opportunities.*
+1.  On the right-side property pane, update the webpage name. For example, *Opportunities.*
 
-5.  Update partial URL. For example, *opportunities.*
+1.  Update partial URL. For example, *opportunities.*
 
-6.  Expand **Permissions**.
+1.  Expand **Permissions**.
 
-7.  Disable **Page available to everyone**.
+1.  Disable **Page available to everyone**.
 
-8.  Select the web roles that should be allowed access to this page.
+1.  Select the web roles that should be allowed access to this page.
 
-9.  Inside the page editor, below the Header section, select the **Column** section.
+1.  Inside the page editor, below the Header section, select the **Column** section.
 
-10. On the left pane, select **Components**.
+1. On the left pane, select **Components**.
 
-11. Under **Portal components**, select **Form**.
+1. Under **Portal components**, select **Form**.
 
-12. On the right-side property pane, select **Use existing**.
+1. On the right-side property pane, select **Use existing**.
 
-13. Under **Name**, select the basic form that you created earlier in this tutorial.
+1. Under **Name**, select the basic form that you created earlier in this tutorial.
 
     > [!TIP]
     > If you don’t see the form available, try **Sync Configuration** to synchronize changes from Dataverse.
 
-14. On the top-right corner, select **Browse website**.
+1. On the top-right corner, select **Browse website**.
 
 The webpage will now show the basic form for the **Opportunities** table with the code component as the slider, similar to how it appears using the model-driven app for the same form.
 
@@ -178,3 +145,4 @@ The webpage will now show the basic form for the **Opportunities** table with th
 [Create your first component](../../developer/component-framework/implementing-controls-using-typescript.md) <br>
 [Add code components to a field or table in model-driven apps](../../developer/component-framework/add-custom-controls-to-a-field-or-entity.md)
 
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]