Live publish

Author: buck1ey

powerapps-docs/developer/common-data-service/define-alternate-keys-entity.md

@@ -2,7 +2,7 @@
 title: "Work with alternate keys (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "The topic explains about how to create alternate keys for an entity. Alternate keys can be created programmatically or by using the customization tools" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 06/24/2020
+ms.date: 08/01/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -23,7 +23,7 @@ All Common Data Service records have unique identifiers defined as GUIDs. These
 
 ## Create alternate keys  
 
-You can create alternate keys programmatically or by using the customizations tools. For more information about using the customization tools, see [Define alternate keys to reference CRM records](https://technet.microsoft.com/library/29e53691-0b18-4fde-a1d0-7490aa227898.aspx).  
+You can create alternate keys programmatically or by using the customizations tools. For more information about using the customization tools, see [Define alternate keys using Power Apps portal](../../maker/common-data-service/define-alternate-keys-portal.md).
 
 To define alternate keys programmatically, you first have to create an object of type <xref:Microsoft.Xrm.Sdk.Metadata.EntityKeyMetadata> (or use <xref href="Microsoft.Dynamics.CRM.EntityKeyMetadata?text=EntityKeyMetadata EntityType" /> if working with Web API). This class contains the key attributes. Once the key attributes are set, you can use `CreateEntityKey` to create the keys for an entity. This message takes the entity name and `EntityKeyMetadata` values as input to create the key.  
 
@@ -54,7 +54,7 @@ You should be aware of the following constraints when creating alternate keys:
 
 - **Unicode characters in key value**
 
-  If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\` then update or upsert (PATCH) actions will not work.  If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
+  If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\`,`?` then retrieve (`GET`), update or upsert (`PATCH`) actions will not work.  If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
 
 <a name="BKMK_crud"></a>   
 

powerapps-docs/maker/common-data-service/define-alternate-keys-portal.md

@@ -2,7 +2,7 @@
 title: "Define alternate keys using Power Apps portal | MicrosoftDocs"
 description: "Learn how to define alternate keys using Power Apps portal"
 ms.custom: ""
-ms.date: 06/11/2020
+ms.date: 08/01/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -28,7 +28,7 @@ search.app:
 Power Apps enables configuring the most common options, but certain options can only be set using solution explorer. More information: [Define alternate keys using solution explorer](define-alternate-keys-solution-explorer.md)
 
 > [!IMPORTANT]
-> If the data within a field that is used in an alternate key will contain one of the following characters /,<,>,*,%,&,:,\ then get or patch actions will not work. If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
+> If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\`,`?` then `GET` or `PATCH` actions will not work. If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
 
 ## View alternate keys
 
@@ -59,4 +59,4 @@ While [viewing alternate keys](#view-alternate-keys), select the key you want to
 
 ### See also
 
-[Developer Documentation: Define alternate keys for an entity](/dynamics365/customer-engagement/developer/define-alternate-keys-entity)
+[Developer Documentation: Work with alternate keys](../../developer/common-data-service/define-alternate-keys-entity.md)

powerapps-docs/maker/common-data-service/define-alternate-keys-solution-explorer.md

@@ -2,7 +2,7 @@
 title: "Define alternate keys using solution explorer | MicrosoftDocs"
 description: "Learn how to define alternate keys that can be used to reference records in Common Data Service using solution explorer"
 ms.custom: ""
-ms.date: 05/31/2018
+ms.date: 08/01/2020
 ms.reviewer: ""
 ms.service: powerapps
 ms.suite: ""
@@ -29,6 +29,9 @@ The [Power Apps portal](https://make.powerapps.com/?utm_source=padocs&utm_medium
 - [Define alternate keys to reference records](define-alternate-keys-reference-records.md)<br />
 - [Define alternate keys using Power Apps portal](define-alternate-keys-portal.md)
 
+> [!IMPORTANT]
+> If the data within a field that is used in an alternate key will contain one of the following characters `/`,`<`,`>`,`*`,`%`,`&`,`:`,`\\`,`?` then `GET` or `PATCH` actions will not work. If you only need uniqueness then this approach will work, but if you need to use these keys as part of data integration then it is best to create the key on fields that won't have data with those characters.
+
 ## Open solution explorer
 
 Part of the name of any alternate key you create is the customization prefix. This is set based on the solution publisher for the solution you’re working in. If you care about the customization prefix, make sure that you are working in an unmanaged solution where the customization prefix is the one you want for this entity. More information: [Change the solution publisher prefix](change-solution-publisher-prefix.md) 
@@ -51,12 +54,13 @@ Part of the name of any alternate key you create is the customization prefix. Th
 1. Select **OK** to close the form.
 
 ### (Optional) View the system job tracking creation of indexes
+
 1. While [viewing alternate keys](#view-alternate-keys) after you have created a new alternate key you will see a row for the key you created.
 2. In the **System Job** column you will find a link to the system job that monitors the creation of the indexes to support the alternate key. 
 
     This system job will have a name that follows this pattern: `Create index for {0} for entity {1}` where `0` is the **Display Name** of the alternate key and `1` is the name of the entity.
 
-    The link to the system job will not be displayed after the system job completes successfully. More information: [Monitor and manage system jobs](/dynamics365/customer-engagement/admin/monitor-manage-system-jobs)
+    The link to the system job will not be displayed after the system job completes successfully. More information: [Monitor and manage system jobs](/power-platform/admin/monitor-manage-system-jobs)
 
 
 ## Delete an alternate key
@@ -67,4 +71,4 @@ While [viewing alternate keys](#view-alternate-keys), select ![Delete](media/del
 
 [Define alternate keys to reference records](define-alternate-keys-reference-records.md)<br />
 [Define alternate keys using Power Apps portal](define-alternate-keys-portal.md)<br />
-[Developer Documentation: Define alternate keys for an entity](/dynamics365/customer-engagement/developer/define-alternate-keys-entity)
+[Developer Documentation: Work with alternate keys](../../developer/common-data-service/define-alternate-keys-entity.md)