SBX - Search With Button

SBX - Forum Post Title

A quick find filter cannot have any child filters

Microsoft Dynamics CRM Forum

Mohan Prasad MAni asked a question on 20 Nov 2018 11:22 PM
My Badges

Question Status

Suggested Answer

While searching the contacts, suddenly in production we started getting the below error

Try this action again. If the problem continues, check the Microsoft Dynamics 365 Community for solutions or contact your organization's Microsoft Dynamics 365 Administrator. Finally, you can contact Microsoft Support. If you contact support, please provide the technical details.

Error Log shows the below error

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: A quick find filter cannot have any child filtersDetail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ActivityId>7535a531-f931-4de7-ab7e-908a362c9697</ActivityId>
<ErrorCode>-2147217118</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic">
<KeyValuePairOfstringanyType>
<d2p1:key>ApiExceptionSourceKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">Plugin/Microsoft.Crm.Common.ObjectModel.AccountService</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiOriginalExceptionKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">Microsoft.Crm.CrmException: A quick find filter cannot have any child filters ---&gt; Microsoft.Crm.CrmException: A quick find filter cannot have any child filters
at Microsoft.Crm.Query.CrmSqlSelectCommandStrategy.QuickFindPredicateBuilder.CreateConditionBuilder(LogicalOperator logicalOperator, EntityMetadata entityMetadata, String tableAlias, DatabaseQueryTarget queryTarget)
at Microsoft.Crm.Query.CrmSqlSelectCommandStrategy.PredicateBuilder.BeginWritingFilter(LogicalOperator filterOperator, EntityMetadata entityMetadata, String tableAlias, DatabaseQueryTarget queryTarget)
at Microsoft.Crm.Query.SelectVisitor.Visit(FilterExpression criteria)
at Microsoft.Crm.Query.SelectVisitor.Visit(FilterExpression criteria)
at Microsoft.Crm.Query.SelectVisitor.Visit(EntityExpression entity)
at Microsoft.Crm.Query.SelectPlan.GenerateUnionInnerQuery()
at Microsoft.Crm.Query.SelectPlan.GetSQLStatement()
at Microsoft.Crm.Query.SelectPlan.&lt;GetSql&gt;b__3_0()
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable`1 additionalCustomProperties)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
at Microsoft.Crm.Query.QueryPlan.get_Command()
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.DoRetrieveMultiple(BusinessEntityCollection entities, EntityExpression entityExp, DatabaseQueryTarget queryTarget, PagingHelper pagingHelper, ExecutionContext context, Boolean needToSetRowVersion, Boolean isVersionNumberRequestedInRetrieve)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.&lt;&gt;c__DisplayClass371_0.&lt;DoRetrieveMultiple&gt;b__0()
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action, IEnumerable`1 additionalCustomProperties)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
at Microsoft.Crm.BusinessEntities.BusinessProcessObject.RetrieveMultiple(EntityExpression entityExpression, DatabaseQueryTarget queryTarget, ExecutionContext context)
--- End of inner exception stack trace ---
at Microsoft.Crm.Extensibility.VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context)
at Microsoft.Crm.Extensibility.PipelineInstrumentationHelper.Execute(Boolean instrumentationEnabled, String stopwatchName, ExecuteWithInstrumentation action, PipelineExecutionContext context)
at Microsoft.Crm.Extensibility.Pipeline.&lt;&gt;c__DisplayClass2_1.&lt;Execute&gt;b__0()</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiStepKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">16ccbb1b-ea3e-db11-86a7-000a3a5473e8</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiDepthKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">1</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiActivityIdKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">7535a531-f931-4de7-ab7e-908a362c9697</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiPluginSolutionNameKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">System</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>ApiStepSolutionNameKey</d2p1:key>
<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">System</d2p1:value>
</KeyValuePairOfstringanyType>
</ErrorDetails>
<Message>A quick find filter cannot have any child filters</Message>
<Timestamp>2018-11-21T04:55:36.8901808Z</Timestamp>
<ExceptionRetriable>false</ExceptionRetriable>
<ExceptionSource i:nil="true" />
<InnerFault i:nil="true" />
<OriginalException i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>

Please advise

 

Reply
N.P@Langate responded on 21 Nov 2018 2:07 AM

We have the same issue from today as well.

Microsoft Dynamics 365, version 1710 (9.1.0.643) online, EU

Reply
Žarko Radevic responded on 21 Nov 2018 2:09 AM

This affects Account entity also in our case, the only way we managed to work around this is to minimize the search columns in quick find view to just one, then it works for both Contact and Account entity.

Reply
Chiron H responded on 21 Nov 2018 2:13 AM

Same problem. Impact on all customers.

1710 (9.1.0.643) online

Reply
adam.orgovanyi responded on 21 Nov 2018 2:15 AM

Actually the searching function is still working, only searching for small parts is having problme.

For example if that field is empty where you are trying to search you can use the magnifying glass just next to it and search in the whole database.

I hope I made it clear, but this is not normal and MS should solve it ASAP.

Reply
David123 responded on 21 Nov 2018 2:17 AM

Same here. Gets error message when searching using a lookup field. Seems to be the same issue on every entity.

Reply
BCoessens responded on 21 Nov 2018 2:17 AM

Same problem here

Version 1710 (9.1.0.643) online

Servicedesk out of business

Reply
thatCRMchick responded on 21 Nov 2018 2:24 AM

Version 1710 (9.1.0.643) online, cannot lookup products to add to the price list. Also submitting a Microsoft support ticket.

Reply
Luks responded on 21 Nov 2018 2:25 AM

Žarko Radevic

This affects Account entity also in our case, the only way we managed to work around this is to minimize the search columns in quick find view to just one, then it works for both Contact and Account entity.

Thanks for sharing this, dude!

Worked also for us as a workaround.

Reply
ISA Martinez responded on 21 Nov 2018 2:29 AM
My Badges

Hi, everyone!

I'm experiencing the same exact problem since this morning. While we wait for MS solution, I workarounded it by doing this:

1. Go to Settings > Customization > Customize the system

2. Locate the Account entity and click on Views

3. Look for the Quick search view for Accounts. It may appear as "Quick find view for active accounts". Double click to open it.

4. Click on "Edit filter criteria".

5. There's a filter to only search on active accounts. Delete the filter.

6. Save and close the view. Publish changes.

7. Refresh (Ctrl + F5) and try again.

Do exactly the same for Contacts.

After doing that we've been able to search again in Accounts and Contacts.

Reply
Jay Rogers responded on 21 Nov 2018 2:30 AM
My Badges

We have the same issue - UK. I've logged a Severity A premier case with Microsoft.

Reply
BCoessens responded on 21 Nov 2018 2:34 AM

When using the "Customer Service Hub" there is no problem. It is only the WEB version that gives problems.

Reply
Joseph Lanjouw responded on 21 Nov 2018 2:35 AM
My Badges

Another temporary solution is to let your clients use the UCI, if you have set up an app and given your organization access: in the UCI searching works perfectly fine.

Reply
Earl J responded on 21 Nov 2018 2:40 AM

Thanks, this worked for us as well

Reply
Johannes O. Zettl responded on 21 Nov 2018 2:40 AM

Version 9.1.0.643 here as well.

There's a workaround concerning lookup fields: The error may pop up when you try to change the existing value of a lookup field -- if you at first clear the value of the field and then click on the magnifying glass, the error doesn't happen.

Good luck!
J.

Reply
Vijay Deshpande responded on 21 Nov 2018 2:44 AM
My Badges

We faced same issue this morning across all our v9.0 instances. We managed to resolve it temporarily by limiting the 'Find columns' to one field. We have also raised a High Severity SR with MS.

Thanks

Reply
Andrew Butenko responded on 20 Nov 2018 11:49 PM
Suggested Answer

Hello,

I'm afraid that you will have to get in touch with Microsoft and open support ticket. I don't think this issue is something you can fix by yourself and looks like a bug.

Reply
Pavel Yaroshenko responded on 21 Nov 2018 2:53 AM
Suggested Answer

Hey

There is some workaround.

Try to turn off all search fields in Quick find view except primary field (example fullname for Contact or accountname for Account etc.)

Reply
Wouter Madou responded on 21 Nov 2018 3:03 AM
My Badges
Suggested Answer

Removing the quick search filter on accounts & contacts was the workaround.

Reply
Brett Lonsdale responded on 21 Nov 2018 4:02 AM
Suggested Answer

We had the same issue this morning. I went to Settings, Customizations, Customize the System. Expand Entities, Then expand the entity that you are trying to search. Click Views. Look for the Quick Find View. Modify the Quick Find View, and clear the filters on the Quick Find View. Save and Close your changes and publish the change. This worked for us.

Reply
Mauro Maniforti responded on 21 Nov 2018 4:07 AM
My Badges
Suggested Answer

Yes, it actually works. I also tried to:
Remove the filter
Publish: Now It Works
Replace the original filter: It works again

It seems that there is a problem of "refreshing" the definition of the query or something related to migration 8.2 -> 9.1

Reply

SBX - Two Col Forum

SBX - Migrated JS