found another topic

Author: JimDaly

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

@@ -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

@@ -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
 

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: 06/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)