acrolinx

Author: JimDaly

powerapps-docs/developer/data-platform/best-practices/business-logic/implement-all-types-of-queries-when-filtering-preoperation-retrievemultiple.md

@@ -49,7 +49,7 @@ This approach potentially changes the expected number of records returned in eac
 
 In the `PreOperation` stage, evaluate the <xref:Microsoft.Xrm.Sdk.IExecutionContext.InputParameters>  <xref:Microsoft.Xrm.Sdk.Messages.RetrieveMultipleRequest.Query> property and adjust the query to filter what is returned before it's executed.
 
-When using this approach you must implement the appropriate filtering for the different possible types of queries, most importantly: <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> and <xref:Microsoft.Xrm.Sdk.Query.QueryExpression>. If you implement just one of these, different applications that use the other type of query won't apply your changes.
+When using this approach you must implement the appropriate filtering for the different possible types of queries, most importantly: <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> and <xref:Microsoft.Xrm.Sdk.Query.QueryExpression>. If you implement just one of these, different applications that use the other type of query don't apply your changes.
 
 Although the `QueryExpressionToFetchXml` and `FetchXmlToQueryExpression` messages provide the capability to convert one query type to another, because of the performance impact of including more calls within `RetrieveMultiple`, we recommend that you don't use these messages in this context. Rather, implement your filtering using the equivalent logic in both. 
 
@@ -69,7 +69,7 @@ When someone writes a plug-in to change the records returned in a specific appli
 
 When using the Web API, GET requests on a collection are converted to <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> unless the query uses FetchXml as described in [Retrieve and execute predefined queries](../../webapi/retrieve-and-execute-predefined-queries.md). In that case the queries use <xref:Microsoft.Xrm.Sdk.Query.FetchExpression>.
 
-Unified Interface replaced the legacy web client for model-driven apps. Unified Interface uses the FetchXml defined in the [SavedQuery.FetchXml](../../reference/entities/savedquery.md#BKMK_FetchXml) or [UserQuery.FetchXml](../../reference/entities/userquery.md#BKMK_FetchXml) properties. For better performance, Unified Interface doesn't convert the FetchXml data to a <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> before executing these queries as the legacy web client did. Therefore, queries that were modified in plug-in code for the legacy web client that used  <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> won't apply the same changes now that the query to support views is being passed using <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> unless the plug-in code is written to apply same logic to <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> queries.
+Unified Interface replaced the legacy web client for model-driven apps. Unified Interface uses the FetchXml defined in the [SavedQuery.FetchXml](../../reference/entities/savedquery.md#BKMK_FetchXml) or [UserQuery.FetchXml](../../reference/entities/userquery.md#BKMK_FetchXml) properties. For better performance, Unified Interface doesn't convert the FetchXml data to a <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> before executing these queries as the legacy web client did. Therefore, queries that were modified in plug-in code for the legacy web client that used  <xref:Microsoft.Xrm.Sdk.Query.QueryExpression> don't apply the same changes now that the query to support views is being passed using <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> unless the plug-in code is written to apply same logic to <xref:Microsoft.Xrm.Sdk.Query.FetchExpression> queries.
 
 <a name='seealso'></a>