Live publish

Author: buck1ey

powerapps-docs/developer/common-data-service/behavior-format-date-time-attribute.md

@@ -34,7 +34,7 @@ If you have users and offices around the world, it is important to properly repr
 |Member name and value|Description|  
 |---------------------------|-----------------|  
 |`UserLocal`|-   Stores the date and time value as UTC value in the system.<br />-   The retrieve operation returns the UTC value.<br />-   The update operation converts the UTC value to the current user’s time zone value, and then stores the updated value as is or as the equivalent UTC value depending on the kind ([DateTimeKind](https://msdn.microsoft.com/library/shx7s921.aspx)) of the value specified for update. If the specified value is of UTC kind, it’s stored as is. Otherwise, the UTC-equivalent value is stored.<br />-   Retrieving the formatted value converts from UTC to the user’s current time zone based on the time zone and locale setting of the user.<br />-   For the Web API, the attribute is exposed as DateTimeOffset.<br />-   This behavior is used for system attributes like `CreatedOn` and `ModifiedOn`, and cannot be changed. You should use this behavior for custom attributes where you want to store date and time values with the time zone information.|  
-|`DateOnly`|-   Stores the actual date value with the time value as 12:00 AM (00:00:00) in the system.<br />-   For the retrieve and update operations, no time zone conversion is performed, and the time value is always 12 AM (00:00:00).<br />-   Retrieving the formatted value displays the date value without any time zone conversion.<br />-   For the Web API, the attribute is exposed as DateTimeOffset.<br />-   This behavior should be used for custom attributes that store birthdays and anniversaries, where the time information is not required.|  
+|`DateOnly`|-   Stores the actual date value with no time value.<br />-   Retrieving the formatted value displays the date value.<br />-   For the Web API, the attribute is exposed as Date.<br />-   This behavior should be used for custom attributes that store birthdays and anniversaries, where the time information is not required.|  
 |`TimeZoneIndependent`|-   Stores the actual date and time values in the system regardless of the user time zone.<br />-   For the retrieve and update operations, no time zone conversion is performed, and actual date and time values are returned and updated respectively in the system regardless of the user time zone.<br />-   Retrieving the formatted value displays the date and time value (without any time zone conversion) based on the format as specified by the current user’s time zone and locale setting.<br />-   For the Web API, the attribute is exposed as DateTimeOffset.<br />-   This behavior should be used for attributes that store information such as check in and check out time for hotels.|  
 
  The following sample code demonstrates how to set a `UserLocal` behavior for a new date time attribute:  

powerapps-docs/maker/common-data-service/data-platform-import-export.md

@@ -5,7 +5,7 @@ author: sabinn-msft
 ms.service: powerapps
 ms.topic: conceptual
 ms.component: cds
-ms.date: 05/14/2018
+ms.date: 08/27/2020
 ms.author: sabinn
 search.audienceType: 
   - maker
@@ -139,3 +139,6 @@ The following data types aren't currently supported.
 - Timezone
 - Multiselect option set
 - Image
+
+    > [!NOTE]
+    > Get Data from Excel and Export Data features are currently not included in the Power Apps Community Plan.

powerapps-docs/maker/model-driven-apps/create-edit-quick-create-forms.md

@@ -2,7 +2,7 @@
 title: "Create or edit model-driven app quick create forms in Power Apps | MicrosoftDocs"
 description: "Learn how to create or edit a quick create form"
 ms.custom: ""
-ms.date: 03/23/2020
+ms.date: 08/28/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -107,7 +107,7 @@ If you add a composite field to a quick create form, it will be displayed as sep
 The **Enable quick create forms** property can be enabled or disabled for all standard activities except recurring appointments. This property lets you change the form that is displayed by default for most activities. By default, the **Enable quick create forms** property is enabled and the quick create form is the form displayed in the app areas and activity entities that support it. 
 
 > [!div class="mx-imgBorder"] 
-> ![](media/allow-quick-create.png "Allow Quick Create property on appointment entity")
+> ![Allow Quick Create property on appointment entity](media/allow-quick-create.png "Allow Quick Create property on appointment entity")
 
 
 ### Unified interface client form display behavior
@@ -160,8 +160,11 @@ When you import a solution from version 8.2 regardless of the value of the **Ena
 
 If there is a customization made in a version 9.0 solution to entities where **Enable quick create forms** is enabled, the value will not change after import.  However, if you have set the **Enable quick create forms** option to *disabled* for the task, phone call, email, and appointment entities, the value will be overwritten to enabled. In this situation, you'll need to reset the **Enable quick create forms** option back to disabled for those activity entities after the import. 
 
-> [!IMPORTANT]
-> Be aware of the behavior that occurs when you create a parent relationship with the same entity. For example, if Account has a relationship to Account and you create a lookup that is used by a quick create form that creates a parent record, the first record will not be saved with the lookup that has the parent record value. This is because of the circular reference introduced by using the same entity. If you experience this issue you can resolve it by removing the parent record id on the quick create form before saving the record.
+[!IMPORTANT]
+>
+> - If a quick create form exists for an entity but is not included in the app, the Unified Interface runtime will still open the quick create form.  This behavior occurs with lookup controls and subgrids. If you don’t want a quick create form to appear in your app you must delete it.
+> - Be aware of the behavior that occurs when you create a parent relationship with the same entity. For example, if Account has a relationship to Account and you create a lookup that is used by a quick create form that creates a parent record, the first record will not be saved with the lookup that has the parent record value. This is because of the circular reference introduced by using the same entity. If you experience this issue you can resolve it by removing the parent record id on the quick create form before saving the record.
+
 
 ### See also  
 [Overview of the form editor user interface](form-editor-user-interface-legacy.md)

powerapps-docs/maker/model-driven-apps/embedded-canvas-app-guidelines.md

@@ -1,7 +1,7 @@
 ---
 title: "Guidelines on working with embedded canvas apps | MicrosoftDocs"
 ms.custom: ""
-ms.date: 08/19/2019
+ms.date: 08/28/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -23,10 +23,11 @@ search.app:
 This topic provides guidelines on working with embedded canvas apps as well as helpful tips to troubleshoot any issues you might encounter.
 
 -	Embedded canvas apps are only supported with Unified Interface model-driven apps.
--	You can only enable one embedded canvas app per form. 
-     - You can have multiple embedded canvas apps added to the form but can only enable one at a time.
-     - If you try to enable more than one embedded canvas app on a model-driven form you will get a message that reads “Only one canvas app can be enabled on a form.”
-     - To enable or disable an embedded canvas app see [Enable an embedded canvas app](#enable-an-embedded-canvas-app) and [Disable an embedded canvas app](#disable-an-embedded-canvas-app).
+-	You can only enable three embedded canvas apps for each form with Web, and one for Tablet and Phone client types. 
+-	You can have multiple embedded canvas apps added to the form, but can only enable three at a time for Web and one at a time for Tablet and Phone client types. 
+-	If you try to enable more than three embedded canvas apps with the Web client type on a model-driven app form you will get the message "You have more than three canvas apps with Web form factor, the maximum is three for this form factor. The number of canvas apps are limited to three for Web and one for Tablet and Phone form factors."
+   - To enable or disable an embedded canvas app see [Enable an embedded canvas app](#enable-an-embedded-canvas-app) and [Disable an embedded canvas app](#disable-an-embedded-canvas-app).
+-	We recommend that you have a single embedded canvas app for each form tab.
 -	When adding an embedded canvas app to a model-driven form always use a required field that is guaranteed to have a value. If your field does not have a value your embedded canvas app will not refresh in response to any change in data on the host model-driven form.
 -	Publishing a model-driven form does not also publish the embedded canvas app.
      - Embedded canvas apps need to be published independent of the host model-driven form. More information: [Publish an app](../canvas-apps/save-publish-app.md#publish-an-app).