Ampersand in Entity Name Causing Filter Lookup Field Error


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):

image

image

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:

image image

image

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!

Advertisements

About Microsoft Dynamics CRM Online

Microsoft Dynamics CRM and CRM Online specialist. Microsoft CRM MVP since 2006
This entry was posted in CRM On Premise, CRM Online, Dynamics 365, Microsoft CRM, MS CRM, Troubleshooting and tagged , . Bookmark the permalink.

2 Responses to Ampersand in Entity Name Causing Filter Lookup Field Error

  1. Tal Simon says:

    Microsoft has large issues with special characters also on field display name since crm 4.
    for example in ISRAEL if you want to use shortcuts naming such as U.N you use ‘ ” ‘ so actually you type U”N.
    doing so will cause lots of trouble when transferring customization or export import template…
    Microsoft needs to wrap and encode all special characters but fail to do so.

  2. Good comment Tal. CRM architecture uses XML a lot – good to note for testing and isolating the issue to check for XML special characters – & ” ‘
    http://xml.silmaril.ie/specials.html

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s