Merge remote-tracking branch 'origin/main' into mspilde-patch-4

Mattp123 · Mattp123 · commit 5afc69f57509 · 2022-04-05T11:32:10.000-07:00
diff --git a/powerapps-docs/developer/component-framework/code-components-alm.md b/powerapps-docs/developer/component-framework/code-components-alm.md
@@ -290,7 +290,7 @@ It's recommended that the MAJOR and MINOR version of the code component's versio
 
 A [Dataverse solution has four parts](/powerapps/maker/data-platform/update-solutions#understanding-version-numbers-for-updates) and it can be thought of in the following structure: `MAJOR.MINOR.BUILD.REVISION`.
 
-If you're using **AzureDevOps**, you can set your build pipeline versioning using the `Build` and `Rev` environment variables ([Run (build) number - Azure Pipelines](/azure/devops/pipelines/process/run-number?view=azure-devops&tabs=yaml&preserve-view=true)), and use PowerShell script similar to the approach described in the article [Use PowerShell scripts to customize pipelines](/azure/devops/pipelines/scripts/powershell?view=azure-devops&tabs=yaml#example-powershell-script-version-assemblies&preserve-view=true).
+If you're using **AzureDevOps**, you can set your build pipeline versioning using the `Build` and `Rev` environment variables ([Run (build) number - Azure Pipelines](/azure/devops/pipelines/process/run-number)), and use PowerShell script similar to the approach described in the article [Use PowerShell scripts to customize pipelines](/azure/devops/pipelines/scripts/powershell#example-powershell-script-version-assemblies).
 
 | Semantic version part | ControlManifest.Input.xml version part<br />`MAJOR.MINOR.PATCH` | Solution.xml version part<br />`MAJOR.MINOR.BUILD.REVISION` | AzureDevOps Build Version                                                                        |
 | --------------------- | --------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
diff --git a/powerapps-docs/developer/data-platform/optimistic-concurrency.md b/powerapps-docs/developer/data-platform/optimistic-concurrency.md
@@ -58,8 +58,8 @@ For information about using Organization service to apply optimistic concurrency
   
      When the **IfVersionMatches** behavior is indicated on an update to a table, and where optimistic concurrency isn’t enabled, a fault is returned.  
   
-You can check the [Code](/dotnet/api/system.servicemodel.faultexception.code?view=netframework-4.6.2&preserve-view=true) property of the returned fault to determine if the fault is related to optimistic concurrency. The codes for the error conditions that were shown previously were obtained from the ErrorCodes.cs helper code.  
-  
+  You can check the [Code](/dotnet/api/system.servicemodel.faultexception.code) property of the returned fault to determine if the fault is related to optimistic concurrency. The codes for the error conditions that were shown previously were obtained from the ErrorCodes.cs helper code.  
+ 
 
 
-[!INCLUDE[footer-include](../../includes/footer-banner.md)]
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/data-platform/powerapps-cli.md b/powerapps-docs/developer/data-platform/powerapps-cli.md
@@ -85,6 +85,28 @@ Launch Visual Studio Code and select the **Extensions** icon, click on the ellip
    > [!div class="mx-imgBorder"]
    > ![Initiate install with the downloaded file.](media/side-load-install-3.png "Install from VSIX")
 
+### Standalone Power Platform CLI
+
+To install standalone Power Platform CLI:
+
+<!--1. Install [Npm](https://www.npmjs.com/get-npm) (comes with Node.js) or [Node.js](https://nodejs.org/en/) (comes with npm). We recommend LTS (Long Term Support) version 10.15.3 LTS because it seems to be the most stable.
+
+1. Install [.NET Framework 4.6.2 Developer Pack](https://dotnet.microsoft.com/download/dotnet-framework/net462). 
+
+1. If you don’t already have Visual Studio 2017 or later, follow one of these options:
+   - Option 1: Install [Visual Studio 2017](/visualstudio/install/install-visual-studio?view=vs-2017) or later.
+   - Option 2: Install [.NET Core 2.2 SDK](https://dotnet.microsoft.com/download/dotnet-core/2.2) and then install [Visual Studio Code](https://code.visualstudio.com/Download)-->
+1. Download and install [Microsoft Power Platform CLI](https://aka.ms/PowerAppsCLI).
+
+1. To take advantage of all the latest capabilities, update Microsoft Power Platform CLI tooling to the latest version by using this command (not applicable for Power Platform VS Code Extension):
+    ```CLI
+    pac install latest
+
+    ```
+> [!NOTE]
+> - Currently, Microsoft Power Platform CLI is supported only on Windows 10 and Windows 11.
+> - Power Platform Tools for Visual Studio Code, and works on Windows 10, Windows 11, Linux, and MacOS.
+
 ## Successful installation
 
 Once the installation is successful, you will need to restart Visual Studio Code, upon which you will see the following notification.
@@ -125,8 +147,7 @@ This table lists some of the common commands used in the CLI.
 
 ## Uninstall Microsoft Power Platform CLI 
 
-To uninstall Microsoft Power Platform CLI tooling, run the MSI installer from [here](/powerapps/developer/data-platform/powerapps-cli).
-
+To uninstall Microsoft Power Platform CLI tooling, run the MSI from [here](/powerapps/developer/data-platform/powerapps-cli).
 
 To uninstall the Visual Studio Code extension, follow the same steps as installing the extension, except this time select the **Uninstall** button.
 
@@ -148,3 +169,5 @@ If you're a Private Preview participant and have an older version of CLI, follow
 
 [Power Apps component framework](../component-framework/overview.md)
 
+
+[!INCLUDE[footer-include](../../includes/footer-banner.md)]
diff --git a/powerapps-docs/developer/data-platform/understand-terminology.md b/powerapps-docs/developer/data-platform/understand-terminology.md
@@ -31,19 +31,18 @@ The data structures that developers work with are exposed as entities, and the t
 
 |To...|Using...|Developers will...|
 |--|--|--|
-|Create a Dataverse table|[Web API](/powerapps/developer/data-platform/webapi/overview)|POST an instance of the [EntityMetadata EntityType](/dynamics365/customer-engagement/web-api/entitymetadata?view=dynamics-ce-odata-9&preserve-view=true) to the `/EntityDefinitions` resource|
-|Create a Dataverse table|[.NET SDK](/powerapps/developer/data-platform/org-service/overview)|Create an instance of the [EntityMetadata Class](/dotnet/api/microsoft.xrm.sdk.metadata.entitymetadata?view=dynamics-general-ce-9&preserve-view=true) and use the [CreateEntityRequest Class](/dotnet/api/microsoft.xrm.sdk.messages.createentityrequest?view=dynamics-general-ce-9&preserve-view=true) to send this to the Organization service|
-|Create a row or record in a Dataverse table|[Web API](/powerapps/developer/data-platform/webapi/overview)|POST data defined as an a specific EntityType. You can find a list of these EntityTypes here: [Web API EntityType Reference](/dynamics365/customer-engagement/web-api/entitytypes?view=dynamics-ce-odata-9&preserve-view=true)|
-|Create a row or record in a Dataverse table|[.NET SDK](/powerapps/developer/data-platform/org-service/overview)|Create an instance of the [Entity Class](/dotnet/api/microsoft.xrm.sdk.entity?view=dynamics-general-ce-9&preserve-view=true) or a class that inherits from it (Account, Contact, etc.) and use the [CreateRequest Class](/dotnet/api/microsoft.xrm.sdk.messages.createrequest?view=dynamics-general-ce-9&preserve-view=true) to send this to the Organization service. A developer can find the information they need to use the Entity class in the [entity reference](/powerapps/developer/data-platform/reference/about-entity-reference).|
-
+|Create a Dataverse table|[Web API](/powerapps/developer/data-platform/webapi/overview)|POST an instance of the [EntityMetadata EntityType](/dynamics365/customer-engagement/web-api/entitymetadata) to the `/EntityDefinitions` resource|
+|Create a Dataverse table|[.NET SDK](/powerapps/developer/data-platform/org-service/overview)|Create an instance of the [EntityMetadata Class](/dotnet/api/microsoft.xrm.sdk.metadata.entitymetadata) and use the [CreateEntityRequest Class](/dotnet/api/microsoft.xrm.sdk.messages.createentityrequest) to send this to the Organization service|
+|Create a row or record in a Dataverse table|[Web API](/powerapps/developer/data-platform/webapi/overview)|POST data defined as an a specific EntityType. You can find a list of these EntityTypes here: [Web API EntityType Reference](/dynamics365/customer-engagement/web-api/entitytypes)|
+|Create a row or record in a Dataverse table|[.NET SDK](/powerapps/developer/data-platform/org-service/overview)|Create an instance of the [Entity Class](/dotnet/api/microsoft.xrm.sdk.entity) or a class that inherits from it (Account, Contact, etc.) and use the [CreateRequest Class](/dotnet/api/microsoft.xrm.sdk.messages.createrequest) to send this to the Organization service. A developer can find the information they need to use the Entity class in the [entity reference](/powerapps/developer/data-platform/reference/about-entity-reference).|
 
 ## Terminology use depending on protocol or technology
 
 The terminology used in the developer documentation depends on the protocol or class library used by developers. 
 
 - When working with the [Web API](/powerapps/developer/data-platform/webapi/overview), we use the terminology defined by the OData protocol. Data structures are defined as *EntityTypes*, which have properties and navigation properties. 
 
-- When working with the [.NET SDK](/powerapps/developer/data-platform/org-service/overview), we use *Entity* because there is an Entity class. The Entity class has an [Attributes](/dotnet/api/microsoft.xrm.sdk.entity.attributes?view=dynamics-general-ce-9&preserve-view=true) property that contains a collection of attributes that are defined by data in an  [AttributeMetadata Class](/dotnet/api/microsoft.xrm.sdk.metadata.attributemetadata?view=dynamics-general-ce-9&preserve-view=true) and many other classes derived from it. 
+- When working with the [.NET SDK](/powerapps/developer/data-platform/org-service/overview), we use *Entity* because there is an Entity class. The Entity class has an [Attributes](/dotnet/api/microsoft.xrm.sdk.entity.attributes) property that contains a collection of attributes that are defined by data in an  [AttributeMetadata Class](/dotnet/api/microsoft.xrm.sdk.metadata.attributemetadata) and many other classes derived from it. 
 
 We use the appropriate terminology to describe the SDK and Web API technology. The developer documentation will *at times* use different terminology than the Power Apps user interface. The table below will help guide you to some of the terminology differences between the developer documentation and rest of the Power Apps documentation. 
 
@@ -53,4 +52,4 @@ We use the appropriate terminology to describe the SDK and Web API technology. T
 | Column         | Attribute           | Property           |
 | Row            | Record              | Record             |
 | Choices        | OptionSet/Picklist  | OptionSet          |
-| Yes/No         | Boolean             | Boolean            |
+| Yes/No         | Boolean             | Boolean            |
diff --git a/powerapps-docs/developer/model-driven-apps/image-web-resources.md b/powerapps-docs/developer/model-driven-apps/image-web-resources.md
@@ -44,7 +44,7 @@ With image web resources you can add images where you need them. Common uses inc
 
 [!INCLUDE[cc-terminology](../data-platform/includes/cc-terminology.md)]
 
-Use Vector Format (SVG) web resources for any icon presented in the application. Vector images are defined as Scalable Vector Graphics (SVG) an XML-based vector image format. The advantage of vector images over other image web resources is that they scale, they are smaller, and if the fill color is removed the model-driven app can control the icon color to avoid contrast issues.  When defining the SVG or before uploading it into the web resource please remove any "fill color" attributes. We recommend using SVG over other image types like PNG and JPG. You can define one vector image and re-use it rather than provide multiple sizes of images. You will use these in with a new <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IconVectorName> property to define the icon for a custom table instead of the `IconLargeName`, `IconMediumName`, or `IconSmallName` properties.
+Use Vector Format (SVG) web resources for any icon presented in the application. Vector images are defined as Scalable Vector Graphics (SVG) an XML-based vector image format. The advantage of SVG over other image web resources is scale, smaller in size, and if the fill color is removed the model-driven app can control the icon color to avoid contrast issues.  When defining the SVG or before uploading it into the web resource please remove any "fill color" attributes. We recommend using SVG over other image types like PNG and JPG. You can define one vector image and re-use it rather than provide multiple sizes of images. You will use these in with a new <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.IconVectorName> property to define the icon for a custom table instead of the `IconLargeName`, `IconMediumName`, or `IconSmallName` properties.
 
 > [!NOTE]
 > Vector Format (SVG) web resources are treated like the [Script (JScript)](./script-jscript-web-resources.md) web resources, and carry the same security risks as Script (JScript) web resources because SVG files allow JScript embedding.
diff --git a/powerapps-docs/includes/cc-privacy-mse-post-and-automation-rules.md b/powerapps-docs/includes/cc-privacy-mse-post-and-automation-rules.md
@@ -1,5 +1,5 @@
 By enabling [!INCLUDE[pn_netbreeze_long](pn-social-engagement-long.md)] to connect to [!INCLUDE[pn_microsoftcrm](pn-microsoftcrm.md)], you will allow data to be sent to [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] using an individual action on a post or automation rules.  
   
- [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] [stores the data](https://go.microsoft.com/fwlink/p/?linkid=867082) from [!INCLUDE[pn_netbreeze_long](pn-social-engagement-long.md)] as a SocialActivity and a SocialProfile entity, and subsequently may convert the SocialActivity into a different record type based on [predefined rules](https://go.microsoft.com/fwlink/p/?LinkID=624394). Any [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] user with the required permission to access [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] records will be able to access and/or process this data.  
+ [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] [stores the data](https://go.microsoft.com/fwlink/p/?linkid=867082) from [!INCLUDE[pn_netbreeze_long](pn-social-engagement-long.md)] as a SocialActivity and a SocialProfile entity, and subsequently may convert the SocialActivity into a different record type based on [predefined rules](/dynamics365/customer-service/set-up-rules-to-automatically-create-or-update-records). Any [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] user with the required permission to access [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)] records will be able to access and/or process this data.  
   
  Note that the data sent from [!INCLUDE[pn_netbreeze_long](pn-social-engagement-long.md)] includes both Social Content and customer data. Specifically, the data includes Social Content information about the social post (author and text) as well as customer data in the form of enriched information, such as sentiment and tags. For complete information about the content of the data sent to [!INCLUDE[pn_crm_shortest](pn-crm-shortest.md)], please see the [payload properties](https://go.microsoft.com/fwlink/p/?LinkID=799094) topic.
diff --git a/powerapps-docs/maker/model-driven-apps/create-remove-pages.md b/powerapps-docs/maker/model-driven-apps/create-remove-pages.md
@@ -2,8 +2,7 @@
 title: "Create and remove pages in model-driven apps | MicrosoftDocs"
 description: Learn how to Create and remove pages in model-driven apps.
 ms.custom: ""
-ms.date: 10/07/2021
-
+ms.date: 03/30/2022
 ms.suite: ""
 ms.tgt_pltfrm: ""
 ms.topic: "get-started-article"
@@ -32,7 +31,10 @@ App designer pages are containers for one or more tables or dashboards. You can
 
 To create a page follow these steps:
 1. Select **New page** in the app designer.
-1. Select the page type of either **Table based view and form** or **Dashboard**, and then select **Next**.
+1. Select the page type, and then select **Next**:  
+   - **Table based view and form**: Display records of a standard or custom table in a full-page list view. Creating a data view page also adds an associated form page for viewing and editing data on a selected record. More information: [Tables in Dataverse](../data-platform/entity-overview.md)
+   - **Dashboard**: Display charts and tables from multiple entities to visualize data on a single page. Select one or more system, interactive, or Power BI dashboards. More information: [Create or edit model-driven app dashboards](create-edit-dashboards.md)
+   - **Custom**: Design and build a page that's based on a canvas app. More information: [Overview of custom pages for model-driven apps](model-app-page-overview.md)
 1. If you don't want your page to appear in the app's site map, clear the **Show in navigation** option.
   :::image type="content" source="media/add-table-view-and-form-pages.png" alt-text="Add table view and form pages":::
 1. Select the components you want.
diff --git a/powerapps-docs/maker/model-driven-apps/model-app-page-issues.md b/powerapps-docs/maker/model-driven-apps/model-app-page-issues.md
@@ -61,8 +61,6 @@ The custom page is a new page type within model-driven apps. Custom pages bring
 
 * When navigating back to a custom page from another page, the page state isn't restored so the page appears like a new navigation.
 
-* 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.
-
 * 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. 
diff --git a/powerapps-docs/mobile/windows-app-use.md b/powerapps-docs/mobile/windows-app-use.md
@@ -172,6 +172,23 @@ With Dataverse search, the search box is always available at the top of every pa
 
 ![Search bar at the top](media/pam-windows-image13.png)
 
+## Set up mobile offline
+
+To configure your app in offline mode, see:
+ 
+- For canvas apps: [Develop offline-capable canvas app](../maker/canvas-apps/offline-apps.md)
+- For model-driven apps: [Set up mobile offline (preview)](setup-mobile-offline.md)
+
+
+## Session ID
+
+If you are having an issues with Power Apps for Windows then send a description of your issue with a screenshot and the session ID to [pamobsup@microsoft.com](mailto:pamobsup@microsoft.com?subject=Power%20Mobile%20issues). 
+
+To see get the session ID, select the More button (...) > **Settings** and then copy the session ID. 
+
+   > [!div class="mx-imgBorder"] 
+   > ![See non-production apps.](media/non-prod-apps.png)
+
 ## Limitations and known issues
 - The following is not supported:
   - Advanced controls such as [sensors](../maker/canvas-apps/how-to/mobile-sensors.md) and [___location](../maker/canvas-apps/functions/signals.md#___location)
