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
MFD responded on 21 Nov 2018 6:02 AM

12:00 pm or 11:22 am gave us just the workaround to delete the filter criteria:

Title: Errors when searching via quick find

User Impact: Users may receive an error when trying to search for a record using quick find.

More Info: When searching for a record via quick find, an error occurs: "A quick find filter cannot have any child filters". As a workaround, users may perform these actions:  

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.

Current Status:  After investigating, we identified the potential source of the issue, and we are attempting to reproduce it to determine the best troubleshooting step to mitigate this issue.

Incident Start Time: Wednesday, November 21, 2018, 3:20 AM UTC

Next Update: Wednesday, November 21, 2018, 2:00 PM UTC

Reply
Bartek Bialik responded on 21 Nov 2018 6:35 AM
My Badges

13:34 CET: problem fixed in my organizations.

I'm able again to quick search account, users and contacts.

And the world is beautiful again.

In fact, CRM is working slower than anything I saw in my life, but it's nothing new.

Reply
hgonzalez responded on 21 Nov 2018 6:42 AM

bialix

13:34 CET: problem fixed in my organizations.

I'm able again to quick search account, users and contacts.

And the world is beautiful again.

In fact, CRM is working slower than anything I saw in my life, but it's nothing new.

Hi bialix, did you test some workaround mentioned in this post or MS Support Center?

Like:

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.

Or it fixed by himself?

In our organizations we just can fix it settin same view and find colums in quick find view and find view for accounts and deleting filter to only search active acounts...

Reply
Ilker Karaoglu responded on 21 Nov 2018 6:54 AM

Guys , the problem solved. But all organizations is loading very slowly.

Reply
MFD responded on 21 Nov 2018 6:56 AM

Newest news:

Current Status:  We identified a misconfigured setting preventing quick find from mapping correctly, causing an error when searching. We performed configuration changes on a test organization and restarted Internet Information Services (IIS), confirming that these steps mitigated the issue. We are currently performing the same steps to all affected customers.

All my systems are working again, no performance issues.

Reply
adam.orgovanyi responded on 21 Nov 2018 7:05 AM

It seems really solved but it was very slow the last 10-20 minutes, but the quick search works again.

Reply
Nicola88 responded on 21 Nov 2018 7:12 AM

I can confirm that the bug is fixed now, and i'm not experiencing big performance issue as someone of you has said.

I want to congratulate with this community for the big sharing :D Together is better :D

Reply
Bartek Bialik responded on 21 Nov 2018 7:51 AM
My Badges

Hi, I tested it, nothing happened when error went berserk :(

It was fixed by Microsoft or gnomes ;)

Reply
valdik responded on 21 Nov 2018 7:58 AM

Microsoft Gnomes™

Reply
Necdet Saritas responded on 21 Nov 2018 8:46 AM
My Badges

Hi all CRM Friends,

There are two new KB release. Please check following link and update your release. We use higher version and we don't have any problem.

support.microsoft.com/.../microsoft-dynamics-crm-online-releases

Reply
Andreas Müller responded on 21 Nov 2018 10:22 AM
My Badges

I can confirm the fix.

No Perfomance issue - everything seems to be working correctly.

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