Merge pull request #3304 from mspilde/patch-13

Update visibility-options-legacy.md

Author: Mattp123

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: 07/23/2020
+ms.date: 08/27/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -29,7 +29,7 @@ search.app:
 
 > [!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). 
+> 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. It is also important to know that the app will not display an error message or block a save if a required field is null and has been disabled. This ensures that users are never blocked from completing a task. To control access, see [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.