Merge pull request #3313 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/powerapps-docs (branch live)

Author: Mattp123

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)