Merge pull request MicrosoftDocs#4292 from MicrosoftDocs/main638169013440288362sync_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

powerapps-docs/maker/portals/configure/entity-forms.md

@@ -64,7 +64,7 @@ To enable permissions for a basic form, select the checkbox to **Enable Table Pe
 |Record Source Type|One of the following values:<ul><li>Query String</li><li>Current Portal User</li><li>Record Associated to Current Portal User</li></ul>Selecting _Query String_ requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the 'Record ID Parameter Name' field.<br>Selecting _Current Portal User_ will retrieve the portal user record for the current authenticated user.<br>Selecting _Record Associated to Current Portal User_ will retrieve the portal user record for the current authenticated user and then retrieve the record for the given relationship as specified by the 'Relationship Name' field.|
 |Record ID Parameter Name|    A parameter name provided in the query string of the URL to the Web Page containing this Basic Form.|
 |Relationship Name|    Required when Record Source Type is Record Associated to Current Portal User. The logical name of the relationship between the current portal user record and the target record. This must return the same table type specified by the Table Name field.|
-|Allow Create If Null|    An optional boolean value available when Record Source Type is Record Associated to Current Portal User. Indicates that if the related record does not exist, allow the user to create it the first time, otherwise an exception will be thrown if the record does not already exist as the form needs a record to data bind to.|
+|Allow Create If Null|    An optional boolean value available when Record Source Type is Record Associated to Current Portal User. Indicates that if the related record does not exist, allow the user to create it the first time, otherwise an exception will be thrown if the record does not already exist as the form needs a record to data bind to. <br> **NOTE**: This feature is not available in multistep forms. |
 |Enable Table Permissions|    Will Cause the form to respect Table Permissions. The default is false for backwards compatibility reasons. If set to true, explicit permissions are REQUIRED for any user wanting to access the form. <br> **NOTE**: This method of securing forms would be deprecated soon. Therefore, it shouldn't be used. Use proper [table permissions](entity-permissions-studio.md), and web role setup to provide access to users for any data instead. More information: [Table permission changes for forms and lists on new portals](../important-changes-deprecations.md#table-permission-changes-for-forms-and-lists-on-new-portals) |
 |||
 
@@ -239,6 +239,5 @@ To disable request validation, follow these steps:
 - [Multistep Forms metadata for portals](configure-web-form-metadata.md)  
 - [Multistep Form subgrid configuration for portals](configure-web-form-subgrid.md)  
 - [Notes configuration for basic forms and Multistep Forms for portals](../configure-notes.md)
-- [Interact with Dataverse data using basic forms](/training/modules/portals-access-data-platform/3-entity-forms)
 
 [!INCLUDE[footer-include](../../../includes/footer-banner.md)]

powerapps-docs/maker/portals/configure/load-form-step.md

@@ -34,7 +34,6 @@ This step type allows the multistep form step to act as a basic form within the
 | Record Source Type                    | One of the following values:<br><ul><li>Query String <br> Selecting Query String requires a parameter name that must be provided in the query string of the URL to the form. This can be specified in the 'Record ID Parameter Name' field.</li><li>Current Portal User <br> Selecting Current Portal User will retrieve the portal user record for the current authenticated user.</li></ul>                                                                                                                                                                                                                                                                                                                                                         |
 | Record ID Parameter Name | A parameter name provided in the query string of the URL to the Web Page containing this Basic Form.                                                                                                                                                                                                                                                                                                                                                                                |
 | Relationship Name                     | Required when Record Source Type is Record Associated to Current Portal User. The logical name of the relationship between the current portal user record and the target record. This must return the same table type specified by the Table Name field.                                                                                                                                                                                                                           |
-| Allow Create If Null                  | An optional Boolean value available when Record Source Type is Record Associated to Current Portal User. Checked indicates that if the related record doesn't exist, allow the user to create it the first time, otherwise an exception will be thrown if the record doesn't already exist because the form needs a record to data-bind to.                                                                                                                                        |
 | Enable Table Permissions             | Will cause the form to respect Table Permissions. The default is false for backwards compatibility reasons. If set to true, explicit permissions are REQUIRED for any user wanting to access the form. This only applies to the FIRST step of a form. <br> **NOTE**: This method of securing forms would be deprecated soon. Therefore, it shouldn't be used. Use proper [table permissions](entity-permissions-studio.md), and web role setup to provide access to users for any data instead. See next section [Secure your forms](#secure-your-forms) details. More information: [Table permission changes for forms and lists on new portals](../important-changes-deprecations.md#table-permission-changes-for-forms-and-lists-on-new-portals)                                                                                                                                                                                                                    |
 ||