locked
Error while persisting option set value from dialog to an entity record RRS feed

  • Question

  • I have created a dialog having 'Prompt and Response' of type Option Set (picklist) and Data Type Integer. Now in the next step (Create Record) when I replace the option set attribute in an entity with that option set response and hit save the Dynamics 365 pops up the error and the option set gets emptied.

    The error text (from the log file):

    System.Xml.XmlException: Name cannot begin with the '>' character, hexadecimal value 0x3E. Line 1, position 59

    I remember this was working in earlier versions. Any ideas, or may I haven't any choice other than to contact Microsoft support?

    Version

    Dynamics 365 9.0.0.2180

    Image 1

    Image 2

    Error Log

    Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Xml.XmlException: Name cannot begin with the '>' character, hexadecimal value 0x3E. Line 1, position 59.
       at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32& colonPos)
       at System.Xml.XmlTextReaderImpl.ParseElement()
       at System.Xml.XmlTextReaderImpl.ParseElementContent()
       at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
       at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
       at System.Xml.XmlDocument.Load(XmlReader reader)
       at Microsoft.Crm.SharedUtil.CreateXmlDocument(XmlReader reader)
       at Microsoft.Crm.SharedUtil.CreateXmlDocument(String xml)
       at Microsoft.Crm.Application.WebServices.WorkflowWebService.UpdateCreateEntityStep(String activityId, String entityId, String createXml, String descriptionXml, String parentStepId, String rendererTypeCode): Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #82EB40ABDetail: 
    <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
      <ActivityId>c547cad7-b564-4158-8b30-31cbf268138b</ActivityId>
      <ErrorCode>-2147220970</ErrorCode>
      <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
      <Message>System.Xml.XmlException: Name cannot begin with the '&gt;' character, hexadecimal value 0x3E. Line 1, position 59.
       at System.Xml.XmlTextReaderImpl.Throw(Exception e)
       at System.Xml.XmlTextReaderImpl.ParseQName(Boolean isQName, Int32 startOffset, Int32&amp; colonPos)
       at System.Xml.XmlTextReaderImpl.ParseElement()
       at System.Xml.XmlTextReaderImpl.ParseElementContent()
       at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
       at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
       at System.Xml.XmlDocument.Load(XmlReader reader)
       at Microsoft.Crm.SharedUtil.CreateXmlDocument(XmlReader reader)
       at Microsoft.Crm.SharedUtil.CreateXmlDocument(String xml)
       at Microsoft.Crm.Application.WebServices.WorkflowWebService.UpdateCreateEntityStep(String activityId, String entityId, String createXml, String descriptionXml, String parentStepId, String rendererTypeCode): Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #82EB40AB</Message>
      <Timestamp>2017-11-30T14:19:28.680789Z</Timestamp>
      <ExceptionRetriable>false</ExceptionRetriable>
      <ExceptionSource i:nil="true" />
      <InnerFault i:nil="true" />
      <OriginalException i:nil="true" />
      <TraceText i:nil="true" />
    </OrganizationServiceFault>

    blog: http://technologynotesforyou.wordpress.com



    • Edited by Khadim Ali Thursday, November 30, 2017 3:44 PM
    Thursday, November 30, 2017 3:33 PM

All replies

  • Update

    This is working perfect in IE browser. However, in chrome it is producing an a server side exception.

    Seems the XML being sent by the client side in chrome is not interpreted correctly by the server side.


    blog: http://technologynotesforyou.wordpress.com

    Monday, December 4, 2017 1:07 PM