Merge branch 'master' into pehecke-solutions-update

Author: phecke

powerapps-docs/developer/common-data-service/powerapps-cli.md

@@ -50,7 +50,7 @@ This table lists some common commands used in the CLI:
 |------|-----------|--------|
 |**pcf**|Commands for working with [Power Apps component framework](/powerapps/developer/component-framework/overview). It has the following parameters: <br/> - **init**: Initializes the code component project. It has the following parameters <br/> - *namespace*: Namespace of the code component. <br/> - *name*: Name of the code component. <br/> - *template*: Field or dataset <br/> - **push**: Pushes the code component to the Common Data Service instance with all the latest changes. It has the following parameter: <br/> - *publisher-prefix*: Publisher prefix of the organization.<br/> - **Version**: Updates the component manifest file with the specified patch version. It has the following parameters: <br/> - *patchversion*: Patch version of the code component. `patchversion` will only take value of the third part of the version tuple: `Major.Minor.Patch`.<br/> - *path*: Absolute or relative path of the component manifest file.<br/> - *allmanifests*: Updates the patch version for all the component manifest files. <br/> - *strategy*: Updates patch version for the manifest files using specified strategy values.| `pac pcf init --namespace <specify your namespace here> --name <Name of the code component> --template <component type>` <br/> <br/> `pac pcf push --publisher-prefix <your publisher prefix>` <br/><br/> `pac pcf version --patchversion <number> --path <Absolute or relative path to component manifest file --allmanifests`  <br/><br/> `pac pcf version --strategy gittags`|
 |**solution**|Commands for working with [Common Data Service solution projects](/powerapps/maker/common-data-service/solutions-overview). It has the following parameters: <br/> - **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. <br/> - **add-reference**: Sets the reference path to the component project folder by passing the `path` parameter.<br/> - **clone**: Creates a solution project based up on the existing solution project by passing 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/> -**Export**: Exports a Common Data Service solution project from the current organization. It has the following parameters:<br/> -*path*: Place where the exported solution zip file will be saved.<br/> - *name*: Name oft he 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 init --publisher-name <enter your publisher name> --publisher-prefix <enter your publisher prefix>` <br/><br/> `pac solution add-reference --path <path to your Power Apps component framework project>`<br/><br/> `pac solution clone –name<name of the solution to be exported> --version <version of your solution> --include <settings that should be included>`|
-|**auth**|Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment). It has the following parameters: <br/> - **create**: Creates the authentication profile for your organization by passing the `url` parameter. Pass the organization url for the `url` parameter. <br/> - **list**: Provides the list of authentication profiles. <br/> - **select**: Provides a way to switch between previously created authentication profiles by passing the `index` parameter.<br/>**delete**: Deletes the authentication profile created by passing  the `index` parameter.|`pac auth create --url <your Common Data Service org’s url>` <br/> <br/> `pac auth list` <br/><br/> `Pac auth select --index <index of the active profile>`|
+|**auth**|Commands to [authenticate to Common Data Service](/powerapps/developer/component-framework/import-custom-controls#connecting-to-your-environment). It has the following parameters: <br/> - **create**: Creates the authentication profile for your organization by passing the `url` parameter. Pass the organization url for the `url` parameter. <br/> - **list**: Provides the list of authentication profiles. <br/> - **select**: Provides a way to switch between previously created authentication profiles by passing the `index` parameter.<br/> - **delete**: Deletes the authentication profile created by passing  the `index` parameter.<br/> - **clear**: Clears all the authentication profile created on the local machine.|`pac auth create --url <your Common Data Service org’s url>` <br/> <br/> `pac auth list` <br/><br/> `pac auth select --index <index of the active profile>`<br/><br/> `pac auth clear`|
 |**telemetry**|Manages the telemetry settings. It has the following parameters: <br/>- *enable*: Enables the telemetry option.<br/> - *disable*: Disables the telemetry option.<br/> - *status*: Returns whether the telemetry is enabled or disabled.|`pac telemetry enable` <br/><br/> `pac telemetry disable`|
 |**org**|Command to work with Common Data Service.|`pac org who`|
 |**plugin**|Manages to create a [plug-in](/powerapps/developer/common-data-service/plug-ins) project|`pac plugin init`|
@@ -76,4 +76,4 @@ If you are a **Private Preview** participant and have an older version of CLI, f
 
 ## See also
 
-[Power Apps component framework](../component-framework/overview.md)
+[Power Apps component framework](../component-framework/overview.md)

powerapps-docs/developer/model-driven-apps/best-practices/business-logic/avoid-window-top.md

@@ -64,7 +64,6 @@ The following are the recommended approaches:
             catch (err) {
                 return false;
             }
-        }
     }
 
     var canAccess = isTopAccessible();

powerapps-docs/maker/canvas-apps/accessible-apps.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: tapanm
-ms.date: 04/03/2018
+ms.date: 07/01/2020
 ms.author: fikaradz
 search.audienceType: 
   - maker
@@ -20,7 +20,7 @@ An accessible canvas app will allow users with vision, hearing and other impairm
 Use the **[Accessibility Checker](accessibility-checker.md)** to help review potential accessibility issues in your app. 
 
 ## Layout and color
-Common sense and uncomplicated design helps apps be more accessible to all users.  When doing heavy customization of apps take note of the below suggestions.  Power Apps themes are by default accessible.
+Common sense and uncomplicated design helps apps be more accessible to all users.  When doing heavy customization of apps take note of the below suggestions. Power Apps themes are designed to meet accessibility standards.
 - Ensure all elements are clearly visible and text is of sufficient size.  All content must be easily read and understood by the naked eye.
 - Avoid using the visibility property of items to bring an element into view.  If you need to show something conditionally, create the content in a new screen and navigate to it and back.
 - Ensure input elements are labeled on the screen. **[AccessibilityLabel](controls/properties-accessibility.md)** property defines what the screen reader will announce.

powerapps-docs/maker/canvas-apps/common-issues-and-resolutions.md

@@ -7,7 +7,7 @@ ms.service: powerapps
 ms.topic: conceptual
 ms.custom: canvas
 ms.reviewer: 
-ms.date: 06/11/2020
+ms.date: 07/02/2020
 ms.author: kvivek
 search.audienceType: 
   - maker
@@ -19,7 +19,7 @@ search.app:
 This article lists some common issues that you might encounter while using Power Apps. Where applicable, workarounds are provided.
 
 1. **Black box covering part of embedded canvas app** (June 11, 2020)
-   When using embedded canvas apps such as SharePoint forms, SharePoint web parts, and model driven forms, users many see a black box when scrolling covering part of the app. This issue happens with chromium based browsers starting with version 83. There is not a workaround at this time. The team is actively investigating to find a fix and workaround.
+   When using embedded canvas apps such as SharePoint forms, SharePoint web parts, and model driven forms, users many see a black box when scrolling covering part of the app. This issue happens with chromium based browsers starting with version 83. There is not a workaround at this time. The team is actively investigating to find a fix and workaround. **A workaround in Power Apps was deployed in the week of 6/21/2020. In addition, the issue is fixed for Microsoft Edge based on Chromium with version 85.**
 
 1. **Problems downloading attachments in SharePoint custom forms** (May 22, 2020)
    When using the attachment control to download an attachment, the click won't have any response when using Google Chrome version 83 or the new Microsoft Edge version 83 browser. As a workaround, change to use the default SharePoint form or use another browser. The team is actively working to fix this issue. **Fix has been deployed in the weeek of 6/8/2020**

powerapps-docs/maker/canvas-apps/getting-started.md

@@ -43,6 +43,7 @@ When you finish the app and save it to the cloud, [share it with others](share-a
 Run your own apps - and any apps shared with you - on Windows, in a [web browser](../../user/run-app-browser.md), or on an [iOS or Android device](../../user/run-app-client.md).
 
 ## Learn more
+- Ready to convert your ideas into an app? Start here: [Planning a Power Apps project](/powerapps/guidance/planning/introduction)
 - Explore the step-by-step, conceptual, and reference topics in the navigation pane on the left.
 - Review [coding standards](https://aka.ms/powerappscanvasguidelines) for maximizing app performance and keeping apps easier to maintain.
 - Check out the [webinars and video gallery](https://powerusers.microsoft.com/t5/Webinars-and-Video-Gallery/bd-p/VideoGallery?featured=yes) to help you leverage the features and functions of Power Apps.
@@ -53,6 +54,7 @@ Run your own apps - and any apps shared with you - on Windows, in a [web browser
 * Create a [support ticket](https://powerapps.microsoft.com/support/pro/) to get technical assistance. If you're a Power Apps administrator for your organization, you can also open a support ticket in the [Power Apps admin center](https://admin.microsoft.com/Support/Support.aspx).
 
 ## Next steps
+- [Planning a Power Apps project](/powerapps/guidance/planning/introduction)
 - [Sign up for a free license](../signup-for-powerapps.md)
 - [Sign in to Power Apps](https://make.powerapps.com?utm_source=padocs&utm_medium=linkinadoc&utm_campaign=referralsfromdoc)
 - [Open a sample app](open-and-run-a-sample-app.md)

powerapps-docs/maker/canvas-apps/limits-and-config.md

@@ -93,7 +93,7 @@ This list identifies all services to which Power Apps Studio talks and their usa
 | graph.microsoft.com<br>graph.windows.net |https |Azure Graph - For getting user info (e.g., profile photo) |
 | gallery.azure.com |https |Sample and Template apps |
 | \*.azure-apim.net |https |Api Hubs - Different sub-domains for each locale |
-| \*.powerapps.com |https | create.powerapps.com, make.powerapps.com, content.powerapps.com, and make.powerapps.com |
+| \*.powerapps.com |https | create.powerapps.com, make.powerapps.com, content.powerapps.com,apps.powerapps.com, and make.powerapps.com |
 | \*.azureedge.net |https | create.powerapps.com, make.powerapps.com, content.powerapps.com, and make.powerapps.com |
 | \*.blob.core.windows.net |https | Blob storage |
 | \*.flow.microsoft.com | https | create.powerapps.com, make.powerapps.com, content.powerapps.com, and make.powerapps.com |

powerapps-docs/maker/model-driven-apps/build-first-model-driven-app.md

@@ -3,14 +3,10 @@ title: Build your first model-driven app from scratch with Power Apps | Microsof
 description: Learn how to build a simple model-driven app
 documentationcenter: ''
 author: Mattp123
-manager: kvivek
-editor: ''
-tags: ''
 ms.service: powerapps
-ms.devlang: na
 ms.topic: conceptual
 ms.component: model
-ms.date: 02/05/2019
+ms.date: 07/01/2020
 ms.author: matp
 search.audienceType: 
   - maker
@@ -23,7 +19,8 @@ search.app:
 Model-driven app design is a component-focused approach to app development. In this topic, you simplify how to create a model-driven app by using one of the standard entities that's available in your Power Apps environment.
 
 > [!TIP]
-> To learn all about building model-driven apps, start here: [Understand model-driven app components](model-driven-app-components.md). 
+> Ready to convert your ideas into an app? Start here: [Planning a Power Apps project](/powerapps/guidance/planning/introduction).<br/> 
+> For detailed information about model-driven apps and how to build it, start here: [Understand model-driven app components](model-driven-app-components.md). 
 
 ## Sign in to Power Apps
 Sign in to [Power Apps](https://make.powerapps.com/). If you don't already have a [!INCLUDE [powerapps](../../includes/powerapps.md)] account, select the **Get started free** link. 

powerapps-docs/maker/model-driven-apps/manage-auto-save.md

@@ -28,7 +28,7 @@ Auto-save helps app users focus on their work without having to manage saving da
 <a name="BKMK_HowAutoSaveWorks"></a>   
 
 ## How auto-save works  
- By default all main forms for [Updated entities and classic entities](create-design-forms.md#updated-versus-classic-entities) will have auto-save enabled. After a record is created (initially saved), any changes made to a form will automatically be saved thirty seconds after the change is made. If no changes are made in the form, the automatic save won't occur while the form is open. After a change is made the 30-second period before an auto-save begins again. The field that someone is currently editing isn't included in an auto-save. If someone else has updated the same record while you're editing it, those changes will be retrieved and displayed in the form when auto-save occurs.  
+ By default all main forms for [Updated entities and classic entities](create-design-forms.md#updated-versus-classic-entities) will have auto-save enabled. After a record is created (initially saved), any changes made to a form will automatically be saved thirty seconds after the change is made. If no changes are made in the form, the automatic save won't occur while the form is open. After a change is made the 30-second period before an auto-save begins again. If someone else has updated the same record while you're editing it, those changes will be retrieved and displayed in the form when auto-save occurs.  
 
  With auto-save enabled, the save button only appears for the initial save of the record. After the record is created, the save button in the command bar isn't shown, but you can see a ![Auto save button](media/auto-save-icon.png "Auto save button") button in the lower right corner that will show if there are any unsaved changes. This control is also displayed if auto-save is disabled.  
 

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

@@ -5,7 +5,7 @@ author: sandhangitmsft
 ms.service: powerapps
 ms.topic: conceptual
 ms.custom: 
-ms.date: 06/25/2020
+ms.date: 06/26/2020
 ms.author: sandhan
 ms.reviewer: tapanm
 ---
@@ -14,6 +14,20 @@ ms.reviewer: tapanm
 
 ## General issues
 
+- 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.*
+
+    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.
+
+    Fields where limit may need to be increased:
+
+    | Entity | Field Display Name |
+    | - | - |
+    | Entity Form | Settings (adx_settings) |
+    | Enity List | View (adx_views) |
+    | Enity Form Metadata | Subgrid Setting (adx_subgrid_settings) |
+
 - 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 Common Data Service model-driven app.
 
 - Because of the ongoing compatibility issues between the updated Yahoo YDN OAuth provider endpoint and Power Apps portals, users are temporarily unable to authenticate with [Yahoo identity provider](./configure/configure-oauth2-settings.md#yahoo-ydn-app-settings).

powerapps-docs/maker/portals/liquid/liquid-types.md

@@ -19,7 +19,7 @@ Liquid objects can return one of seven basic types: **String**, **Number**, **Bo
 A String is declared by wrapping text in single or double quotes.
 
 ```
-{% assign string_a = Hello World! %}
+{% assign string_a = "Hello World!" %}
 
 {% assign string_b = 'Single quotes work too.' %}
 ```
@@ -121,4 +121,4 @@ This will render if the ID request parameter is NOT null.
 [Conditional](liquid-conditional-operators.md)  
 [Liquid Objects](liquid-objects.md)  
 [Liquid Tags](liquid-tags.md)  
-[Liquid Filters](liquid-filters.md)  
+[Liquid Filters](liquid-filters.md)