You’re offline. This is a read only version of the page.
70
Hi everyone,
I'm hoping someone may be able to help as an error has started occurring seemingly at random within our CRM system. When creating an appointment and browsing for which account to assign to the appointment we are getting a Query Builder Error. If I type in more than the first couple of letter and hit 'Enter' the error occurs or if I leave the field empty, click on the browse button and choose 'Look up more records' the error occurs.
The downloaded log file shows details of the error as below. Having had a look at other posts on here about Query Builder Errors most seemed to be related to custom entities being removed or amended but no changes like that have been made in our system recently.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: The entity with ObjectTypeCode = 10008 was not found in the MetadataCache.Detail:
<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">
<ErrorCode>-2147217150</ErrorCode>
<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>The entity with ObjectTypeCode = 10008 was not found in the MetadataCache.</Message>
<Timestamp>2016-06-24T14:03:53.1792801Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</OrganizationServiceFault>
Any assistance with trying to identify the cause of this error would be greatly appreciated.
Thanks
*This post is locked for comments
I have the same question (0)
Update: Looks like there was some java script being used on the appointment form to restrict the regarding lookup to search for only accounts and not other record types. I've disabled the java script and the error is no longer occurring. This was setup months ago by third party developers who set up our CRM system and despite being enabled in dev, uat and production environments only production and uat seemed to be affected with the error.
Share
Report
All responses (
Answers (
