diff --git a/Posh-IBWAPI/en-US/Posh-IBWAPI-help.xml b/Posh-IBWAPI/en-US/Posh-IBWAPI-help.xml
index 12bd343..3f8d362 100644
--- a/Posh-IBWAPI/en-US/Posh-IBWAPI-help.xml
+++ b/Posh-IBWAPI/en-US/Posh-IBWAPI-help.xml
@@ -301,7 +301,9 @@
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="Filters">
           <maml:name>Filter</maml:name>
           <maml:description>
-            <maml:para>A string array of search filter conditions (e.g. "name%7E=myhost","ipv4addr=10.10.10.10") or hashtable (e.g. @{'name~'='myhost';ipv4addr='10.10.10.10'}). All conditions must be satisfied to match an object. String based filters must be properly URL encoded. Hashtable filters will be automatically URL encoded. See Infoblox WAPI documentation for advanced usage details.</maml:para>
+            <maml:para>A hashtable with search filter conditions (e.g. `@{'name~'='myhost';ipv4addr='10.10.10.10'}`). All conditions must be satisfied to match an object. The filters can also be specified as an array of strings but the field names and values must be URL encoded by the caller in advance (e.g. `"name%7E=myhost","ipv4addr=10.10.10.10"`). With both methods, all conditions must be satisfied to match an object.</maml:para>
+            <maml:para>NOTE: WAPI field names are case sensitive. The value specified for a field is also case sensitive unless using the case insensitive modififer, `:`, or accounting for case via regex.</maml:para>
+            <maml:para>See Infoblox WAPI documentation for advanced usage details.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
           <dev:type>
@@ -456,7 +458,9 @@
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="Filters">
           <maml:name>Filter</maml:name>
           <maml:description>
-            <maml:para>A string array of search filter conditions (e.g. "name%7E=myhost","ipv4addr=10.10.10.10") or hashtable (e.g. @{'name~'='myhost';ipv4addr='10.10.10.10'}). All conditions must be satisfied to match an object. String based filters must be properly URL encoded. Hashtable filters will be automatically URL encoded. See Infoblox WAPI documentation for advanced usage details.</maml:para>
+            <maml:para>A hashtable with search filter conditions (e.g. `@{'name~'='myhost';ipv4addr='10.10.10.10'}`). All conditions must be satisfied to match an object. The filters can also be specified as an array of strings but the field names and values must be URL encoded by the caller in advance (e.g. `"name%7E=myhost","ipv4addr=10.10.10.10"`). With both methods, all conditions must be satisfied to match an object.</maml:para>
+            <maml:para>NOTE: WAPI field names are case sensitive. The value specified for a field is also case sensitive unless using the case insensitive modififer, `:`, or accounting for case via regex.</maml:para>
+            <maml:para>See Infoblox WAPI documentation for advanced usage details.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
           <dev:type>
@@ -610,7 +614,9 @@
       <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="Filters">
         <maml:name>Filter</maml:name>
         <maml:description>
-          <maml:para>A string array of search filter conditions (e.g. "name%7E=myhost","ipv4addr=10.10.10.10") or hashtable (e.g. @{'name~'='myhost';ipv4addr='10.10.10.10'}). All conditions must be satisfied to match an object. String based filters must be properly URL encoded. Hashtable filters will be automatically URL encoded. See Infoblox WAPI documentation for advanced usage details.</maml:para>
+          <maml:para>A hashtable with search filter conditions (e.g. `@{'name~'='myhost';ipv4addr='10.10.10.10'}`). All conditions must be satisfied to match an object. The filters can also be specified as an array of strings but the field names and values must be URL encoded by the caller in advance (e.g. `"name%7E=myhost","ipv4addr=10.10.10.10"`). With both methods, all conditions must be satisfied to match an object.</maml:para>
+          <maml:para>NOTE: WAPI field names are case sensitive. The value specified for a field is also case sensitive unless using the case insensitive modififer, `:`, or accounting for case via regex.</maml:para>
+          <maml:para>See Infoblox WAPI documentation for advanced usage details.</maml:para>
         </maml:description>
         <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
         <dev:type>
diff --git a/docs/Functions/Get-IBObject.md b/docs/Functions/Get-IBObject.md
index 6467b49..783edf3 100644
--- a/docs/Functions/Get-IBObject.md
+++ b/docs/Functions/Get-IBObject.md
@@ -123,8 +123,10 @@ Accept wildcard characters: False
 ```
 
 ### -Filter
-A string array of search filter conditions (e.g. "name%7E=myhost","ipv4addr=10.10.10.10") or hashtable (e.g. @{'name~'='myhost';ipv4addr='10.10.10.10'}). All conditions must be satisfied to match an object.
-String based filters must be properly URL encoded. Hashtable filters will be automatically URL encoded.
+A hashtable with search filter conditions (e.g. `@{'name~'='myhost';ipv4addr='10.10.10.10'}`). All conditions must be satisfied to match an object. The filters can also be specified as an array of strings but the field names and values must be URL encoded by the caller in advance (e.g. `"name%7E=myhost","ipv4addr=10.10.10.10"`). With both methods, all conditions must be satisfied to match an object.
+
+NOTE: WAPI field names are case sensitive. The value specified for a field is also case sensitive unless using the case insensitive modififer, `:`, or accounting for case via regex.
+
 See Infoblox WAPI documentation for advanced usage details.
 
 ```yaml