Live publish

Author: buck1ey

.openpublishing.redirection.json

@@ -5,6 +5,16 @@
       "redirect_url": "create-solution#solution-publisher",
       "redirect_document_id": "false"
     },
+    {
+      "source_path": "powerapps-docs/user/run-canvas-and-model-apps-on-mobile.md",
+      "redirect_url": "../mobile/run-powerapps-on-mobile",
+      "redirect_document_id": "false"
+    },
+    {
+      "source_path": "powerapps-docs/user/powerapps_mobile_troubleshoot.md",
+      "redirect_url": "powerapps-mobile-troubleshoot",
+      "redirect_document_id": "false"
+    },
     {
       "source_path": "powerapps-docs/maker/canvas-apps/monitor.md",
       "redirect_url": "../monitor-canvasapps",

powerapps-docs/developer/data-platform/powerapps-cli.md

@@ -5,7 +5,7 @@ keywords: Power Apps CLI, code components, component framework, CLI
 ms.author: nabuthuk
 author: Nkrb
 manager: kvivek
-ms.date: 01/25/2021
+ms.date: 02/10/2021
 ms.service: "powerapps"
 ms.suite: ""
 ms.tgt_pltfrm: ""
@@ -90,7 +90,7 @@ Command to work with solution packages. It has the following parameters:
 
 
 
-### Pcf
+### PCF
 
 Commands to work with [Power Apps component framework](/powerapps/developer/component-framework/overview). It has the following parameters:
 
@@ -114,7 +114,10 @@ Commands for working with [Dataverse solution projects](/powerapps/maker/data-pl
 |init|Initializes the solution project.  It has the following parameters:<br/>  - *publisher-name*: Publisher name of the organization. <br/>  - *publisher-prefix*: Publisher prefix of the organization.|`pac solution init --publisher-name developer --publisher-prefix dev`  |
 |add-reference|Sets the reference path to the component project folder by passing the `path` parameter.|`pac solution add-reference --path c:\Users\Downloads\SampleComponent`|
 |clone|Creates a solution project based up on the existing solution project. It has the following parameters:<br/> -*name*: The name of the solution to be exported.<br/> -*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported. <br/> It has the following values: autonumbering, calendar, customization, emailtracking, externalapplications, general, isvconfig, marketing, outlooksynchronization, relationshiproles, sales|`pac solution clone -–name  sampleSolution --version 1.0.0.2 --include general`|
-|export|Exports a Dataverse solution project from the current organization. It has the following parameters:<br/> -*path*: Complete file name where the exported solution zip file will be saved.<br/> - *name*: Name of the solution that needs to be exported.<br/> - *managed*: Defines whether the solution should be exported as a managed solution or not.<br/>-*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.|`pac solution export --path c:\Users\Documents\Solution.zip -- name SampleComponentSolution --managed true --targetversion 10.0.03 --include general`|
+|import|Imports a Dataverse solution to an environment. It requires that you are connected to an environment [Auth commands](#auth) and has the following parameters:<br/>  -*activate-plugins*: Activates plug-ins and workflows in the environment after the import (alias: -ap). <br/>  -*async*: Imports the solution asynchronously (alias: -a). <br/>  -*force-overwrite*: Forces an overwrite of unmanaged customizations (alias: -f). <br/>  -*import-as-holding*: Imports the solution as a holding solution (alias: -h). <br/>  -*max-async-wait-time*: Maximum asynchronous wait time in minutes. Default value is 60 mintues (alias: -wt). <br/>  -*path*: Path to solution zip file. If not specified, assumes the current folder (alias: -p). <br/>  -*publish-changes*: Publishes changes after successful import (alias: -pc). <br/>  -*skip-dependency-check*: Skips dependency check against dependencies flagged as product update (alias: -s). |`pac solution import --path c:\Users\Documents\Solution.zip `|
+|export|Exports a Dataverse solution from an environment. It requires that you are connected to an environment [Auth commands](#auth) and has the following parameters:<br/> -*path*: Complete file name where the exported solution zip file will be saved.<br/> - *name*: Name of the solution that needs to be exported.<br/> - *managed*: Defines whether the solution should be exported as a managed solution or not.<br/>-*targetversion*: The version that the exported solution supports.<br/> -*include*: Settings that should be included in the solution being exported.|`pac solution export --path c:\Users\Documents\Solution.zip -- name SampleComponentSolution --managed true --targetversion 10.0.03 --include general`|
+|list|List all Solutions from a Dataverse environment. It requires that you are connected to an environment [Auth commands](#auth). This command has no parameters:|`pac solution list`  |
+
 
 ### Auth
 

powerapps-docs/maker/TOC.yml

@@ -29,8 +29,6 @@
   items:
   - name: In a browser
     href: ../user/run-app-browser.md
-  - name: On a mobile device
-    href: ../user/run-canvas-and-model-apps-on-mobile.md
   - name: On a SharePoint Online page (canvas apps)
     href: ../user/powerapps-web-part.md
   - name: In Microsoft Teams (canvas apps)
@@ -1320,7 +1318,7 @@
   - name: Create push notifications for Power Apps mobile
     href: ../mobile/power-apps-mobile-notification.md
   - name: Troubleshoot issues for the Power Apps mobile app
-    href: ../user/powerapps_mobile_troubleshoot.md
+    href: ../user/powerapps-mobile-troubleshoot.md
 
 - name: Portals
   items:

powerapps-docs/maker/canvas-apps/controls/control-combo-box.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: reference
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 07/06/2020
+ms.date: 02/11/2021
 ms.author: chmoncay
 search.audienceType: 
   - maker
@@ -18,13 +18,13 @@ search.app:
 A control that allows users to make selections from provided choices.  Supports search and multiple selections.
 
 ## Description
-A **Combo box** control allows you to search for items you will select.  The search is performed server-side on the SearchField property so performance is not affected by very large data sources.  
+A **Combo box** control allows you to search for items you will select.  The search is performed server-side on the SearchField property so performance is not affected by large data sources.  
 
 Single or multi-select mode is configured via the SelectMultiple property.
 
 When searching for items to select, for each item you can choose to show a single data value, two values, or a picture and two values (Person) by modifying the Layout settings in the Data pane.
 
-When viewing on small screens, the items list flyout will become a full screen control for better usablility.
+When viewing on small screens, the items list flyout will become a full screen control for better usability.
 
 > [!NOTE]
 > If you want to search for items with *numbers*, convert numbers to text with [Text()](https://docs.microsoft.com/powerapps/maker/canvas-apps/functions/function-text) function. For example, *Text(12345)*.
@@ -43,7 +43,13 @@ To use **Combo box** as a people picker, choose the **Person** template from the
 
 **IsSearchable** – Whether the user can search for items before selecting.
 
-**SearchFields** - The data fields of the data source searched when user is entering text.  To search on multiple fields, set ComboBox1.SearchFields = ["MyFirstColumn", "MySecondColumn"]
+> [!NOTE]
+> **IsSearchable** can be enabled only on a data source that contains at least one text field. The **Items** expression must be delegable for queries to be delegated with searching. That is, **If** statements within the **Items** expression are not supported.
+
+**SearchFields** - The data fields of the data source searched when user is entering text.  
+
+> [!NOTE]
+> To search on multiple fields, set ComboBox1.SearchFields = ["MyFirstColumn", "MySecondColumn"].  Only text fields are supported.
 
 ## Additional properties
 **[AccessibleLabel](properties-accessibility.md)** – Label for screen readers.
@@ -64,13 +70,13 @@ To use **Combo box** as a people picker, choose the **Person** template from the
 
 **[Height](properties-size-___location.md)** – The distance between a control's top and bottom edges.
 
-**InputTextPlaceholder** – Instructional text shown to end-users when no items are selected.
+**InputTextPlaceholder** – Instructional text shown to end users when no items are selected.
 
 **OnChange** – How the app responds when the user changes a selection.
 
-**OnNavigate** – How the app responds when the user clicks on an item.
+**OnNavigate** – How the app responds when the user selects an item.
 
-**[OnSelect](properties-core.md)** – How the app responds when the user taps or clicks a control.
+**[OnSelect](properties-core.md)** – How the app responds when the user taps or selects a control.
 
 **[TabIndex](properties-accessibility.md)** – Keyboard navigation order in relation to other controls.
 

powerapps-docs/maker/canvas-apps/dependent-drop-down-lists.md

@@ -2,12 +2,11 @@
 title: Create a dependent drop-down list in a canvas app | Microsoft Docs
 description: In Power Apps, create a drop-down list that filters another drop-down list in a canvas app.
 author: emcoope-msft
-manager: kvivek
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 04/04/2019
+ms.date: 02/11/2021
 ms.author: emcoope
 search.audienceType: 
   - maker
@@ -22,7 +21,8 @@ As a best practice, create a data source for the values in the "parent" and "chi
 
 For the scenario in this topic, store employees submit issues to an **Incidents** list through a form. Employees specify not only the ___location of the store at which the incident occurred but also the department within that ___location. Not all locations have the same departments, so a **Locations** list ensures that employees can't specify a department for a ___location that doesn't have that department.
 
-This topic uses Microsoft SharePoint lists as data sources, but all tabular data sources work the same way.
+> [!NOTE]
+> This article uses Microsoft SharePoint lists as data sources, but all tabular data sources work the same way. Within [Dataverse for Teams](../../teams/create-apps-overview.md), you'll need to enable [classic controls](../../teams/understand-power-apps-studio.md#classic-controls) to get the classic drop-down to work for this scenario.
 
 ## Create data sources
 

powerapps-docs/maker/portals/known-issues.md

@@ -5,7 +5,7 @@ author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 06/26/2020
+ms.date: 02/12/2021
 ms.author: sandhan
 ms.reviewer: tapanm
 ---
@@ -23,9 +23,9 @@ ms.reviewer: tapanm
 
 - You receive the following error message when configuring or using entity fields:
 
-    ***Field Name**: You have exceeded the maximum number of 100000 characters in this field.*
+    ***Field Name**: You have exceeded the maximum number of X characters in this field.*
 
-    This can happen if the referenced field for the entity exceeds 100000 characters limit. To increase this limit, go to your Dynamics 365 instance > **Settings** > **Customization** > **Customize this system** > **Components** > **Entities**. Select applicable entity and then select the field. Increase the **Maximum Length** field value for the field to a higher value. Allowed values: 1 through 1,048,576.
+    This can happen if the referenced field for the entity exceeds characters limit mentioned in the error. To increase this limit, go to your Dynamics 365 instance > **Settings** > **Customization** > **Customize this system** > **Components** > **Entities**. Select applicable entity and then select the field. Increase the **Maximum Length** field value for the field to a higher value. Allowed values: 1 through 1,048,576.
 
     Fields where limit may need to be increased:
 
@@ -34,6 +34,7 @@ ms.reviewer: tapanm
     | Entity Form | Settings (adx_settings) |
     | Enity List | View (adx_views) |
     | Enity Form Metadata | Subgrid Setting (adx_subgrid_settings) |
+    | Web Page | Copy (adx_copy) |
 
 - Rich-text for notes in timeline isn't fully supported by Power Apps portals because there's no rich-text editor equivalent control available in portals. For more information, go to [notes created with rich-text editor](configure-notes.md?#notes-created-with-rich-text-editor). If you want, you can [disable the rich-text editor for notes in timeline](https://docs.microsoft.com/powerapps/maker/model-driven-apps/set-up-timeline-control#enable-or-disable-rich-text-editor-for-notes-in-timeline) for the Microsoft Dataverse model-driven app.
 

powerapps-docs/mobile/run-powerapps-on-mobile.md

@@ -21,13 +21,21 @@ searchScope:
 
 # Run model-driven apps and canvas apps on Power Apps mobile
 
-When you create an app, or someone shares an app with you—either a canvas app or model-driven app—you can run that app on iOS and Android devices by using the Power Apps mobile app. If you're on a Windows device, you can only run canvas apps; model-driven apps aren't supported on [Power Apps for Windows](https://www.microsoft.com/en-us/p/power-apps/9nblggh5z8f3?activetab=pivot:overviewtab). In this topic, you'll learn how to get started and run a canvas app and a model-driven app on your mobile device. 
+When you create an app, or someone shares an app with you—either a [canvas app](https://docs.microsoft.com/powerapps/maker/#canvas-apps) or [model-driven](https://docs.microsoft.com/powerapps/maker/#model-driven-apps) app—you can run that app on iOS and Android devices by using the Power Apps mobile app. 
 
-To learn how to use model-driven apps running on the Power Apps mobile app, see [User Guide for model-driven apps running on the Power Apps mobile app](use-custom-model-driven-app-on-mobile.md).
+If you're on a Windows device, you can only run canvas apps; model-driven apps aren't supported on [Power Apps for Windows](https://www.microsoft.com/p/power-apps/9nblggh5z8f3?activetab=pivot:overviewtab). Also, Power Apps for Windows isn't supported if you have the [Power Apps per app plan](/power-platform/admin/about-powerapps-perapp).
 
-> [!IMPORTANT]
-> - Customer engagement apps (such as Dynamics 365 Sales and Dynamics 365 Customer Service) don't run in the Power Apps mobile app. Instead, you use the Dynamics 365 for phones and tablets apps. More information: [User Guide for Dynamics 365 for phones and tablets](https://docs.microsoft.com/dynamics365/mobile-app/dynamics-365-phones-tablets-users-guide).
-> - Power Apps for Windows isn't supported if you have the [Power Apps per app plan](/power-platform/admin/about-powerapps-perapp).
+
+| **App type**  | **iOS** |**Android** |**Windows** |
+| --- | --- |--- |--- |
+| **[Model-driven](https://docs.microsoft.com/powerapps/maker/#model-driven-apps)** |X |X| |
+| **[Canvas](https://docs.microsoft.com/powerapps/maker/#canvas-apps)** |X |X|X|
+
+
+> [!NOTE]
+> Customer engagement apps (such as Dynamics 365 Sales and Dynamics 365 Customer Service) don't run in the Power Apps mobile app. Instead, you use the Dynamics 365 for phones and tablets apps. More information: [User Guide for Dynamics 365 for phones and tablets](https://docs.microsoft.com/dynamics365/mobile-app/user-guide-mobile-app).
+
+In this topic, you'll learn how to get started and run a canvas app and a model-driven app on your mobile device 
 
 ![Power Apps mobile user interface.](media/powerappsmobile.png "Power Apps mobile user interface")
 
@@ -65,13 +73,13 @@ Choose the download link for your device:
 - For Android, go to [Google Play](https://play.google.com/store/apps/details?id=com.microsoft.msapps). 
 
 
-## Open Power Apps, and sign in
+## Sign in
 
 Open Power Apps on your mobile device, and sign in by using your Azure Active Directory credentials.
 
-![Sign in to Power Apps.](media/powerapps_mobile_app_signin_screen.png "Sign in to Power Apps")
+If you have the Microsoft Authenticator app installed on your mobile device, enter your username when prompted, and then approve the notification sent to your device. If you run into issues signing in, see [Troubleshoot sign in issues](https://docs.microsoft.com/en-us/powerapps/user/powerapps_mobile_troubleshoot#sign-in-issues).
 
-If you have the Microsoft Authenticator app installed on your mobile device, enter your username when prompted, and then approve the notification sent to your device.
+![Sign in to Power Apps.](media/powerapps_mobile_app_signin_screen.png "Sign in to Power Apps")
 
 
 ## Find the app
@@ -226,7 +234,7 @@ If an app requires a connection to a data source or permission to use the device
 
 ![Give consent to a canvas app.](media/give_consent_canvas.jpg "Give consent to canvas app")
 
-### Run a model-driven app 
+### Use a model-driven app 
 
 The following image shows an example of a model-driven app screen after you've signed in. To learn how to use model-driven apps running on the Power Apps mobile app, go to [User Guide for model-driven apps running on the Power Apps mobile app](use-custom-model-driven-app-on-mobile.md). 
 
@@ -247,6 +255,7 @@ Select the site map ![Site map icon](media/pa_mobile_sitemap_icon.png "Site map
 
 ## See also
 
+[User Guide for model-driven apps running on the Power Apps mobile app](use-custom-model-driven-app-on-mobile.md) <br/>
 [Troubleshoot issues for the Power Apps mobile app](https://docs.microsoft.com/powerapps/user/powerapps_mobile_troubleshoot)
 
 

powerapps-docs/mobile/use-custom-model-driven-app-on-mobile.md

@@ -22,7 +22,7 @@ search.app:
 Use the Power Apps mobile app to run model-driven apps on your mobile device. For more information about how to install and get started with an app, see [Run model-driven apps and canvas apps on Power Apps mobile](run-powerapps-on-mobile.md).
 
 > [!IMPORTANT]
-> Model-driven apps for Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Field Service don't run in the Power Apps mobile app. Instead, you use the Dynamics 365 for phones and tablets app. For more information, see [User Guide for Dynamics 365 for phones and tablets](https://docs.microsoft.com/dynamics365/mobile-app/dynamics-365-phones-tablets-users-guide).
+> Model-driven apps for Dynamics 365 Sales, Dynamics 365 Customer Service, and Dynamics 365 Field Service don't run in the Power Apps mobile app. Instead, you use the Dynamics 365 for phones and tablets app. For more information, see [User Guide for Dynamics 365 for phones and tablets](https://docs.microsoft.com/dynamics365/mobile-app/user-guide-mobile-app).
 
 ## Home screen 
 

powerapps-docs/teams/known-issues-limitations.md

@@ -54,7 +54,7 @@ There is no enforcement of user-created required table fields. Rows that have em
 
 ### Classic controls
 
-Enabling classic controls requires a refresh of Power Apps Studio.  
+Enabling [classic controls](understand-power-apps-studio.md#classic-controls) requires a refresh of Power Apps Studio.  
 
 ### Canvas components