acrolinx

Author: JimDaly

powerapps-docs/developer/data-platform/configure-entity-relationship-cascading-behavior.md

@@ -27,7 +27,7 @@ More information: [Create a One-to-Many relationship using Web API](webapi/creat
 
 ## Using Organization Service to configure cascading behavior
 
-When you use <xref:Microsoft.Xrm.Sdk.Messages.CreateOneToManyRequest> or <xref:Microsoft.Xrm.Sdk.Messages.UpdateRelationshipRequest> you include an instance of a <xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata> class in the body of the request. In the <xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.CascadeConfiguration> property of that class you use the <xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguration> class.  
+When you use <xref:Microsoft.Xrm.Sdk.Messages.CreateOneToManyRequest> or <xref:Microsoft.Xrm.Sdk.Messages.UpdateRelationshipRequest>, you include an instance of a <xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata> class in the body of the request. In the <xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.CascadeConfiguration> property of that class you use the <xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguration> class.  
 
 The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguration> class or <xref:Microsoft.Dynamics.CRM.CascadeConfiguration?text=CascadeConfiguration ComplexType>) contains the properties representing actions that may be performed on the referenced table in the one-to-many relationship. Each property can be assigned one of the values of the <xref:Microsoft.Dynamics.CRM.CascadeType?text=CascadeType EnumType>.  
 
@@ -42,7 +42,7 @@ The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguratio
 
 **Active Records considered for Cascading action**
 
-Cascading actions on active records will only include records that have a state code of "Active". The following State Codes for these tables, are considered Active for Cascade actions. Different labels (other than Active) may be used for this state code in different tables. Any custom state or status code with values other than below will not be processed as an active record for cascading purposes.
+Cascading actions on active records only include records that have a state code of "Active". The following State Codes for these tables, are considered Active for Cascade actions. Different labels (other than Active) may be used for this state code in different tables. Any custom state or status code with values other than below won't be processed as an active record for cascading purposes.
 
 | Table Name                       |    State Code 0       |    State Code 1       |    State Code 2       |    State Code 3       | 
 | :--------------------------------| :----------------:    | :----------------:    | :----------------:    | :-----------------:    |
@@ -79,7 +79,7 @@ The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguratio
 |------------|-----------------|-------------------|  
 |Assign|The referenced table record owner and/or business unit is changed.|Active<br />Cascade<br />NoCascade<br />UserOwned|  
 |Delete|The referenced table record is deleted. **Note:**  The options for this action are limited.|Cascade<br />RemoveLink<br />Restrict|  
-|Merge|The record is merged with another record. **Note:**  For referenced tables that can be merged, Cascade is the only valid option. In other cases use NoCascade.|Cascade<br />NoCascade|  
+|Merge|The record is merged with another record. **Note:**  For referenced tables that can be merged, Cascade is the only valid option. In other cases, use NoCascade.|Cascade<br />NoCascade|  
 |Reparent|See [About the reparent action](#about-the-reparent-action) later.|Active<br />Cascade<br />NoCascade<br />UserOwned|  
 |Share|When the referenced table record is shared with another user.|Active<br />Cascade<br />NoCascade<br />UserOwned|  
 |Unshare|When sharing is removed for the referenced table record.|Active<br />Cascade<br />NoCascade<br />UserOwned|  
@@ -97,10 +97,11 @@ The `CascadeConfiguration` (<xref:Microsoft.Xrm.Sdk.Metadata.CascadeConfiguratio
 > if they want to continue using it.
 
 ### About the assign action
-The assign action allows the owner, the Owning Business Unit or both owner and business unit updates to be cascaded down to all child records when the parent record is updated.
+
+The assign action allows the owner, the Owning Business Unit, or both owner and business unit updates to be cascaded down to all child records when the parent record is updated.
 
 #### Allowed record ownership across business units not enabled
-When the [allow record ownership across business units](/power-platform/admin/wp-security-cds#to-enable-this-matrix-data-access-structure-preview) is not enabled, the Owning Business Unit column can't be explicitly updated when changing the record's owner. The following lists the cascading behaviors when the parent's record owner is updated.
+When the [allow record ownership across business units](/power-platform/admin/wp-security-cds#to-enable-this-matrix-data-access-structure-preview) isn't enabled, the Owning Business Unit column can't be explicitly updated when changing the record's owner. The following lists the cascading behaviors when the parent's record owner is updated.
 
 If you update the owner:
 
@@ -112,8 +113,8 @@ If you update the owner:
 - Cascade assign set to None
   - Record owner is updated to the new owner
   - Record business unit is updated to new owner's business unit
-  - Child records' owner is not updated (no cascade)
-  - Child records' business unit is not updated (no cascade)
+  - Child records' owner isn't updated (no cascade)
+  - Child records' business unit isn't updated (no cascade)
 
 #### Allowed record ownership across business units is enabled
 
@@ -134,23 +135,23 @@ the Owning Business Unit column can be explicitly updated when changing the reco
    - Cascade assign set to None
      - Record owner is updated to the new owner
      - Record business unit is updated to new owner's business unit
-     - Child records' owner is not updated (no cascade)
-     - Child records' business unit is not updated (no cascade)
+     - Child records' owner isn't updated (no cascade)
+     - Child records' business unit isn't updated (no cascade)
 
 2. If you update the business unit:
 
    **AlwaysMoveRecordToOwnerBusinessUnit** = true (default)
 
     - Default cascade assign behavior (cascade all)
-      -   Record owner is not updated
+      -   Record owner isn't updated
       -   Record business unit is updated to new business unit
-      -   Child records' owner is not updated 
+      -   Child records' owner isn't updated 
       -   Child records' business unit is updated to new business unit
     - Cascade assign set to None
-      -   Record owner is not updated
+      -   Record owner isn't updated
       -   Record business unit is updated to new business unit
-      -   Child records' owner is not updated 
-      -   Child records' business unit is not updated
+      -   Child records' owner isn't updated 
+      -   Child records' business unit isn't updated
 
 3. If you update the owner and business unit:
 
@@ -164,12 +165,12 @@ the Owning Business Unit column can be explicitly updated when changing the reco
    - Cascade assign set to None
      - Record owner is updated to the new owner
      - Record business unit is updated to new business unit
-     - Child records' owner is not updated
-     - Child records' business unit is not updated 
+     - Child records' owner isn't updated
+     - Child records' business unit isn't updated 
 
 #### Change the cascade behaviors with the OrgDBSettings AlwaysMoveRecordToOwnerBusinessUnit
 
-You can set **AlwaysMoveRecordToOwnerBusinessUnit** to false; the user owned records' Business unit is not moved to the new user's business unit.
+You can set **AlwaysMoveRecordToOwnerBusinessUnit** to false; the user owned records' Business unit isn't moved to the new user's business unit.
 
 **AlwaysMoveRecordToOwnerBusinessUnit** can be set in [environment database settings](/power-platform/admin/environment-database-settings) and can also be set using the [OrgDBOrgSettings tool for Microsoft Dynamics CRM](https://support.microsoft.com/help/2691237/orgdborgsettings-tool-for-microsoft-dynamics-crm).
 
@@ -179,29 +180,29 @@ You can set **AlwaysMoveRecordToOwnerBusinessUnit** to false; the user owned rec
 
    - Default cascade assign behavior (cascade all)
      - Record owner is updated to the new owner
-     - Record business unit is not updated 
+     - Record business unit isn't updated 
      - Child records' owner is updated to the new owner
-     - Child records' business unit is not updated 
+     - Child records' business unit isn't updated 
    - Cascade assign set to None
      - Record owner is updated to the new owner
-     - Record business unit is not updated 
-     - Child records' owner is not updated
-     - Child records' business unit is not updated 
+     - Record business unit isn't updated 
+     - Child records' owner isn't updated
+     - Child records' business unit isn't updated 
 
 2. If you update the business unit:
 
    **AlwaysMoveRecordToOwnerBusinessUnit** = false
 
    - Default cascade assign behavior (cascade all)
-     -   Record owner is not updated
+     -   Record owner isn't updated
      -   Record business unit is updated to new business unit
-     -   Child records' owner is not updated 
+     -   Child records' owner isn't updated 
      -   Child records' business unit is updated to new business unit
    - Cascade assign set to None
-     -   Record owner is not updated
+     -   Record owner isn't updated
      -   Record business unit is updated to new business unit
-     -   Child records' owner is not updated 
-     -   Child records' business unit is not updated
+     -   Child records' owner isn't updated 
+     -   Child records' business unit isn't updated
 
 3. If you update the owner and business unit:
 
@@ -215,8 +216,8 @@ You can set **AlwaysMoveRecordToOwnerBusinessUnit** to false; the user owned rec
    - Cascade assign set to None
      - Record owner is updated to the new owner
      - Record business unit is updated to new business unit
-     - Child records' owner is not updated
-     - Child records' business unit is not updated
+     - Child records' owner isn't updated
+     - Child records' business unit isn't updated
 
 > [!NOTE]
 > When **AlwaysMoveRecordToOwnerBusinessUnit** = false
@@ -237,13 +238,13 @@ You can set **AlwaysMoveRecordToOwnerBusinessUnit** to false; the user owned rec
 
 ### About the reparent action
 
-The reparent action is very similar to the share action except that it deals with the inherited access rights instead of explicit access rights. The reparent action is when you change the value of the referencing column in a parental relationship. When a reparent action occurs, the desired scope of the inherited  access rights for related tables might change for ReadAccess, WriteAccess, DeleteAccess, AssignAccess, ShareAccess, AppendAccess and AppendToAccess. It will not change for CreateAccess. The cascade actions related to the reparent action refer to changes to access rights indicated above for the table record and any table records related to it.  
+The reparent action is similar to the share action except that it deals with the inherited access rights instead of explicit access rights. The reparent action is when you change the value of the referencing column in a parental relationship. When a reparent action occurs, the desired scope of the inherited  access rights for related tables might change for ReadAccess, WriteAccess, DeleteAccess, AssignAccess, ShareAccess, AppendAccess and AppendToAccess. It doesn't change for CreateAccess. The cascade actions related to the reparent action refer to changes to access rights indicated above for the table record and any table records related to it.  
 
 <a name="BKMK_MergeAction"></a>
 
 ### About the merge action
 
-The merge action can sometimes have problems completing if a record that is part of the operation set is deleted while the merge system job is running. Often this will result in an error indicating that the record will be "differently parented" or the child record "might lose its parenting". If this occurs, and you would prefer the merge continue forward even if the record is missing, you can choose to disable the parent check when you select the columns to merge.
+The merge action can sometimes have problems completing if a record that is part of the operation set is deleted while the merge system job is running. Often this results in an error indicating that the record will be "differently parented" or the child record "might lose its parenting". If this occurs, and you would prefer the merge continue forward even if the record is missing, you can choose to disable the parent check when you select the columns to merge.
 
 
 > [!NOTE]