Live publish

Author: buck1ey

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

@@ -2,7 +2,7 @@
 title: "Create or edit model-driven app quick view forms in Power Apps | MicrosoftDocs"
 description: "Learn how to create or edit a quick view form"
 ms.custom: ""
-ms.date: 03/13/2020
+ms.date: 07/23/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -85,6 +85,9 @@ A quick view form can be added to another form as a quick view control. It provi
 
 7.  To save the form select **Save**.  
 
+    > [!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.
+
 ## Next steps   
  [Create and design forms](create-design-forms.md)   
  [Create or edit quick create forms](create-edit-quick-create-forms.md)

powerapps-docs/maker/model-driven-apps/visibility-options-legacy.md

@@ -2,7 +2,7 @@
 title: "Show or hide model-driven app form elements with Power Apps | MicrosoftDocs"
 description: "Learn how to display or hide from elements, such as tabs, sections, or fields"
 ms.custom: ""
-ms.date: 06/11/2018
+ms.date: 07/23/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -27,8 +27,9 @@ search.app:
 
  Several types of form elements have the option to be shown or hidden by default. Tabs, sections, fields, iFrames, and web resources all provide this option. Using form scripts or business rules the visibility of these elements can be controlled to create a dynamic form to provide a user interface that adapts to conditions in the form.  
 
-> [!NOTE]
+> [!IMPORTANT]
 >  Hiding form elements is not a recommended way to enforce security. There are several ways people can view all the elements and data in the form when elements are hidden. 
+> Disabling, hiding, or locking a field, control, or form component using the form designer, manually in the form XML, or using a Client API only works to control data access in a Unified Interface or legacy web client app. It doesn’t strictly enforce data access by itself in the apps. Moreover, it doesn’t control data access using other ways to connect to Common Data Service such as using the Web service or a canvas app. To control access, [Set security roles for a form](control-access-forms.md#set-security-roles-for-a-form) or use [Field-level security](/power-platform/admin/field-level-security). 
   
  Rather than designing forms that depend on scripts to control visibility of options, consider whether a business process flow, a dialog, or switching to a different form may be better suited to meet your requirements. If you do use scripts, make sure that any element that might be hidden is hidden by default. Only show it with scripts when your logic calls for it. This way it will not be displayed in presentations that do not support scripts.