During design testing for a Client: I had encountered the following error when trying to enter a value in a Filter Lookup field for search/entry with the latest Microsoft Dynamics 365 (CRM) Online (also observed in Dynamics CRM 2015):
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Xml.XmlException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #256F659DDetail:
<OrganizationServiceFault xmlns:i=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://schemas.microsoft.com/xrm/2011/Contracts”>
<ActivityId>c94ea082-fdfa-429c-884f-b0d432b9bc5c</ActivityId>
<ErrorCode>-2147220970</ErrorCode>
<ErrorDetails xmlns:d2p1=”http://schemas.datacontract.org/2004/07/System.Collections.Generic” />
<Message>System.Xml.XmlException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #256F659D</Message>
<Timestamp>2017-03-20T19:01:41.5723237Z</Timestamp>
<ExceptionSource i:nil=”true” />
<InnerFault i:nil=”true” />
<OriginalException i:nil=”true” />
<TraceText i:nil=”true” />
</OrganizationServiceFault>
Unfortunately, the above error is not much help. After some trouble-shooting: the variable causing the issue was an ampersand “&” sign on one of the filtered condition values:
Note: this ampersand “&” sign on one of the filtered condition values affects various field types including text field
Workarounds:
- Wait for future bug fix
- Update the value and remove any ampersand “&” sign
- Setup another field to be used in the filtered. The value in this field does NOT contain any ampersand “&” sign
Contact me if you are looking for some Microsoft Dynamics 365 CRM/Sales help.
Frank Lee, Microsoft Business Solutions MVP Dynamics 365 CRM/Sales
San Francisco Bay Area Silicon Valley
Workopia, Inc. – CRM Keeping it Simple!
