Live publish

Author: buck1ey

powerapps-docs/developer/data-platform/org-service/samples/Create-retrieve-entity-relationships.md

@@ -1,8 +1,8 @@
 ---
-title: "Sample: Create and retrieve entity relationships  (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "This sample shows how to create and retrieve entity relationships." # 115-145 characters including spaces. This abstract displays in the search result.
+title: "Sample: Create and retrieve table relationships  (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "This sample shows how to create and retrieve table relationships." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 06/17/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "samples"
@@ -16,11 +16,11 @@ search.app:
   - D365CE
 ---
 
-# Create and retrieve entity relationships
+# Create and retrieve table relationships
 
 [!INCLUDE[cc-data-platform-banner](../../../../includes/cc-data-platform-banner.md)]
 
-This sample shows how to create and retrieve entity relationships. The following methods are used to create and retrieve the relationships:
+This sample shows how to create and retrieve table relationships. The following methods are used to create and retrieve the relationships:
 
 - [CreateOneToManyRequest](/dotnet/api/microsoft.xrm.sdk.messages.createonetomanyrequest?view=dynamics-general-ce-9)
 - [CreateManyToManyRequest](/dotnet/api/microsoft.xrm.sdk.messages.createmanytomanyrequest?view=dynamics-general-ce-9)
@@ -31,13 +31,15 @@ This sample shows how to create and retrieve entity relationships. The following
 
 You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/CreateRetrieveEntityRelationships).
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 ## How to run this sample
 
 [!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
 
 ## What this sample does
 
-The `CreateOneToManyRequest`, `CreateManyToManyRequest`, `CanManyToManyRequest`, `CreateOneToManyRequest`, `CanBeReferencedRequest`, `CanBeReferencingRequest`, and `RetrieveRelationshipRequest` messages are intended to be used in a scenario where it contains the data that is needed to create and retrieve entity relationships.
+The `CreateOneToManyRequest`, `CreateManyToManyRequest`, `CanManyToManyRequest`, `CreateOneToManyRequest`, `CanBeReferencedRequest`, `CanBeReferencingRequest`, and `RetrieveRelationshipRequest` messages are intended to be used in a scenario where it contains the data that is needed to create and retrieve table relationships.
 
 ## How this sample works
 
@@ -51,13 +53,13 @@ Checks for the current version of the org.
 
 1. The `CreateOneToManyRequest` method creates a new One-to-Many (1:N) relationship. 
 2. The `CreateManyToManyRequest` method creates a new Many-To-Many (N:N) relationship.
-3. The `EligibleCreateManyToManyRelationship` method verifies whether entities can participate in N:N relationship.
-4. The `RetrieveRelationshipRequest` method retrieves the two entity relationships previously created.
+3. The `EligibleCreateManyToManyRelationship` method verifies whether tables can participate in N:N relationship.
+4. The `RetrieveRelationshipRequest` method retrieves the two tables relationships previously created.
 
 
 ### Clean up
 
-Display an option to delete the records created in the [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the records created in the [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/add-record-queue-early-bound.md

@@ -2,7 +2,7 @@
 title: "Sample: Add a record to queue (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample shows how to add a record to a queue." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 06/17/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "samples"
@@ -21,6 +21,8 @@ search.app:
 
 This sample shows how to add a record to a queue. It creates source and destination queues. It adds a letter activity to the source queue and then moves it to the destination queue. You can download the sample from [here](https://github.com/Microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/RecordToQueue).
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 This sample requires additional users that are not in your system. Create the users manually in **Microsoft 365** in order to run the sample without any errors. For this sample, create a user profile **as is** shown below. 
 
 **First Name**: Kevin<br/>
@@ -34,7 +36,7 @@ This sample requires additional users that are not in your system. Create the us
 
 ## What this sample does
 
-The `AddToQueueRequest` message is intended to be used in a scenario where it contains data that is needed to move an entity record from a source queue to destination queue.
+The `AddToQueueRequest` message is intended to be used in a scenario where it contains data that is needed to move a table record from a source queue to destination queue.
 
 ## How this sample works
 
@@ -44,8 +46,8 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 1. Checks for the current version of the org.
 2. The `Queue` method creates source and destination queues and store their returned GUIDs in variable.
-3. Creates a Letter entity.
-4. The `AddToQueueRequest` method adds an entity record into a queue, in this sample it associates the letter with first queue.
+3. Creates a Letter table.
+4. The `AddToQueueRequest` method adds a table record into a queue, in this sample it associates the letter with first queue.
 5. Retrieves the user created manually in **Microsoft 365** for assigning the queue items to the user's queue.
 
 ### Demonstrate
@@ -55,7 +57,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 ### Clean up
 
-Display an option to delete the sample data that is created in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data that is created in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/add-security-principal-user-team-queue-early-bound.md

@@ -21,6 +21,8 @@ search.app:
 
 This sample showcases how to give a user or a team access to a queue. The [AddPrincipalToQueueRequest](/dotnet/api/microsoft.crm.sdk.messages.addprincipaltoqueuerequest?view=dynamics-general-ce-9) adds the specified principal to the list of queue members. If the passed-in security principal is a team each member of the team is added to the queue. You can download the sample from [here](https://github.com/Microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AddSecurityPrincipalToQueue).
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 ## How to run this sample
 
 [!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
@@ -48,7 +50,7 @@ The `AddPrincipalToQueueRequest` method adds the team to the queue.
 
 ### Clean up
 
-Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/assign-chart-to-another-user.md

@@ -22,6 +22,8 @@ search.app:
 
 This sample shows how to assign a user-owned visualization to another using the [AssignRequest](/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message. You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AssignChartToAnotherUser).
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 This sample requires an additional user that isn't available in your system. Create the required user manually in **Microsoft 365** in order to run the sample without any errors. For this sample create a user profile **as is** shown below. 
 
 **First Name**: Kevin<br/>
@@ -45,15 +47,15 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 1. Checks for the current version of the org.
 2. The `CreateRequiredRecords` method creates a sample account and some opportunity records for the visualization.
-3. The `newUserOwnedVisualization` method creates the visualization entity instance.
+3. The `newUserOwnedVisualization` method creates the visualization table instance.
 
 ### Demonstrate
 
 The `AssignRequest` method assigns the visualization or chart to the newly created user.
 
 ### Clean up
 
-Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/assign-dashboard-to-another-user.md

@@ -22,6 +22,8 @@ search.app:
 
 This sample shows how to assign a user-owned visualization to another using the [AssignRequest](/dotnet/api/microsoft.crm.sdk.messages.assignrequest?view=dynamics-general-ce-9) message. Because you can’t delete a user-owned dashboard that is assigned to another user, this sample shows how to use impersonation to delete the user-owned dashboard. You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AssignUserOwnedDashboardToAnother).
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 This sample requires an additional user that isn't available in your system. Create the required user manually in **Microsoft 365** in order to run the sample without any errors. For this sample create a user profile **as is** shown below. 
 
 **First Name**: Kevin<br/>
@@ -44,7 +46,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-2. The `CreateRequiredRecords` method creates entity records that this sample requires.
+2. The `CreateRequiredRecords` method creates table records that this sample requires.
 3. The `mySavedQuery` method grabs the default public view for the opportunities.
 4. The `visualizationQuery` method retrieves the visualizations out of the system. This sample assumes that you have the **Top opportunities**. 
 5. The `_otherUSerId` method creates the user to whom the dashboard will be assigned.
@@ -55,7 +57,7 @@ The `AssignRequest` method assigns the visualization or chart to the newly creat
 
 ### Clean up
 
-Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/associate-security-role-team.md

@@ -24,6 +24,8 @@ This sample shows how to assign a security role to a team by using the [AssignRe
 
 You can download the sample from [here](https://github.com/microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AssociateSecurityRoleToTeam)
 
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
+
 ## How to run this sample
 
 [!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
@@ -48,7 +50,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 ### Clean up
 
-Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/associate-security-role-user.md

@@ -55,7 +55,7 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 
 ### Clean up
 
-Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/audit-entity-data-changes.md

@@ -1,8 +1,8 @@
 ---
-title: "Sample: Audit entity data changes (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
-description: "This sample showcases how to audit entity data changes" # 115-145 characters including spaces. This abstract displays in the search result.
+title: "Sample: Audit table data changes (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
+description: "This sample showcases how to audit table data changes" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 06/17/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "samples"
@@ -15,19 +15,21 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Sample: Audit entity data changes
+# Sample: Audit table data changes
 
 [!INCLUDE[cc-data-platform-banner](../../../../includes/cc-data-platform-banner.md)]
 
-This sample shows how to enable and disable auditing on an entity and its attributes, retrieve the data change history of the audited entity, and delete the audit records. You can download the sample from [here](https://github.com/Microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AuditEntityData).
+This sample shows how to enable and disable auditing on a table and its columns, retrieve the data change history of the audited table, and delete the audit records. You can download the sample from [here](https://github.com/Microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AuditEntityData).
+
+[!INCLUDE[cc-terminology](../../includes/cc-terminology.md)]
 
 ## How to run this sample
 
 [!include[cc-how-to-run-samples](../../includes/cc-how-to-run-samples.md)]
 
 ## What this sample does
 
-The `RetrieveRecordChangeHistoryRequest` message is intended to be used in a scenario where it contains data that is needed to retrieve the audit history for an entity.
+The `RetrieveRecordChangeHistoryRequest` message is intended to be used in a scenario where it contains data that is needed to retrieve the audit history for a table.
 
 
 ## How this sample works
@@ -37,17 +39,17 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-2. Creates an sample account entity.
+2. Creates an sample account table.
 
 ### Demonstrate
 
 1. Gets the organization's ID from the system user record.
-2. Enabling auditing on organization and also on the sample account entity.
-3. The `RetrieveRecordChangeHistoryRequest` retrieves the audit history for the account entity and displays the result.
+2. Enabling auditing on organization and also on the sample account table.
+3. The `RetrieveRecordChangeHistoryRequest` retrieves the audit history for the account table and displays the result.
 
 ### Clean up
 
-Display an option to delete the sample data that is created in [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the sample data that is created in [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]

powerapps-docs/developer/data-platform/org-service/samples/audit-user-access.md

@@ -2,7 +2,7 @@
 title: "Sample: Audit user access (Microsoft Dataverse) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This sample shows how to audit user access" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 10/31/2018
+ms.date: 06/17/2021
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -19,8 +19,6 @@ search.app:
 
 [!INCLUDE[cc-data-platform-banner](../../../../includes/cc-data-platform-banner.md)]
 
-<!-- https://docs.microsoft.com/dynamics365/customer-engagement/developer/sample-audit-user-access -->
-
 This sample code shows how to audit user access. You can download the sample from [here](https://github.com/Microsoft/PowerApps-Samples/tree/master/cds/orgsvc/C%23/AuditUserAccess).
 
 ## How to run this sample
@@ -29,7 +27,7 @@ This sample code shows how to audit user access. You can download the sample fro
 
 ## What this sample does
 
-This sample first enables user access auditing with the logged on user's organization. Next, it creates and modifies an account entity so that audit records are genertated.
+This sample first enables user access auditing with the logged on user's organization. Next, it creates and modifies an account table so that audit records are generated.
 
 ## How this sample works
 
@@ -38,18 +36,18 @@ In order to simulate the scenario described in [What this sample does](#what-thi
 ### Setup
 
 1. Checks for the current version of the org.
-1. Creates a new account entity and enables auditing on the new account entity.
+1. Creates a new account table and enables auditing on the new account table.
 
 ### Demonstrate
 
 1. Gets the organization's ID from the system user record and retrieves organization record.
 2. Enables auditing on the organization, including auditing for user access.
-3. Makes an update request to the account entity to be tracked by auditing.
+3. Makes an update request to the account table to be tracked by auditing.
 4. set the organization and account auditing flags back to old values and retrieve them if they were actually changed.
 
 ### Clean up
 
-Display an option to delete the records created during [Setup](#setup). The deletion is optional in case you want to examine the entities and data created by the sample. You can manually delete the records to achieve the same result.
+Display an option to delete the records created during [Setup](#setup). The deletion is optional in case you want to examine the tables and data created by the sample. You can manually delete the records to achieve the same result.
 
 
 [!INCLUDE[footer-include](../../../../includes/footer-banner.md)]