diff --git a/powerapps-docs/developer/data-platform/webapi/query-data-web-api.md b/powerapps-docs/developer/data-platform/webapi/query-data-web-api.md
index 479c1650d8..692b881a54 100644
--- a/powerapps-docs/developer/data-platform/webapi/query-data-web-api.md
+++ b/powerapps-docs/developer/data-platform/webapi/query-data-web-api.md
@@ -896,10 +896,31 @@ GET [Organization URI]/api/data/v9.2/accounts?$select=name,numberofemployees
 Keep the following points in mind when you filter on string values:
 
 - All filters using string values are case insensitive.
+- You must URL encode special characters in filter criteria. More information: [URL encode special characters](#url-encode-special-characters)
 - You may use wildcard characters, but avoid trailing wildcards. More information: [Use wildcard characters](#use-wildcard-characters)
 - You can use OData query functions: `contains`, `startswith`, and `endswith`. More information: [Use OData query functions](#use-odata-query-functions)
 - You must manage single quotes when you use filters that accept an array of string values. More information: [Manage single quotes](#manage-single-quotes)
 
+#### URL encode special characters
+
+If the string you are using as a value in a filter function includes a special character, you need to URL encode it. For example, if you use this function: `contains(name,'+123')`, it will not work because `+` is a character that can't be included in a URL. If you URL encode the string, it will become `contains(name,'%2B123')` and you will get results where the column value contains `+123`.
+
+The following table shows the URL encoded values for common special characters.
+
+|Special<br />character|URL encoded<br />character|
+|---|---|
+|`$`|`%24`|
+|`&`|`%26`|
+|`+`|`%2B`|
+|`,`|`%2C`|
+|`/`|`%2F`|
+|`:`|`%3A`|
+|`;`|`%3B`|
+|`=`|`%3D`|
+|`?`|`%3F`|
+|`@`|`%40`|
+
+
 #### Use wildcard characters
 
 When composing filters using strings, you can apply the following wildcard characters:
diff --git a/powerapps-docs/includes/cc-postoperation-description.md b/powerapps-docs/includes/cc-postoperation-description.md
index 486cc07c14..04ae9fd727 100644
--- a/powerapps-docs/includes/cc-postoperation-description.md
+++ b/powerapps-docs/includes/cc-postoperation-description.md
@@ -1 +1 @@
-Occurs after the main system operation and within the database transaction.<br /><br />Use this stage to modify any properties of the message before it is returned to the caller.<br /><br />Avoid applying changes to an entity included in the message because this will trigger a new Update event.<br /><br />Within the PostOperation stage you can register steps to use the asynchronous execution mode. These steps will run outside of the database transaction using the asynchronous service. <br />More information [Asynchronous service](/powerapps/developer/data-platform/asynchronous-service).
+Occurs after the main system operation and within the database transaction.<br /><br />Use this stage to modify any properties of the message before it is returned to the caller.<br /><br />Avoid applying changes to an entity included in the message because this will trigger a new Update event.<br /><br />Within the PostOperation stage you can register steps to use the asynchronous execution mode. These steps will run outside of the database transaction using the asynchronous service.<br /><br />You must use asynchronous mode when registering your plug-in if the plug-in is designed to perform an update operation and is registered on the Create message of the [User (SystemUser)](/power-apps/developer/data-platform/reference/entities/systemuser) entity. <p/>More information: [Asynchronous service](/powerapps/developer/data-platform/asynchronous-service).