There is no doubt that Dynamics 365 has come up with so many exiting features. Along with new branding Dynamics 365 brought many updates. Many are available for both Online and On-Premises, some – for now – are Online only.
But Hold On, Not all well for those who are using ADXStudio Portals for Dynamics 365.
or
If you have ADXStudio Portal integrated with your CRM instance and you are planning to upgrade it to Dynamics 365.
Today i would like to give some information about the ADXStudio Portal issues that you might face while upgrading your CRM instance to Dynamics 365.
Issue 1 : If you have exposed CRM Activity form (phonecall, email, task, any custom activity etc) on Portal as Entity Form, you might face this issue :
Server Error in ‘/’ Application.
A saved query for entity “interactionforemail” with the querytype “64” and isdefault “True” could not be found.
…
Exception Details: System.ApplicationException: A saved query for entity “entitlement” with the querytype “64” and isdefault “True” could not be found.
Resolution :
As per the ADX Community, This issue is due to use of OOB Activity Regarding field on Portal Entity Form.To get around this issue you will need to remove the “regarding” field from the form. If you need to assign a value you might use a workflow. We are looking into ways of supporting this field for a future release.
https://community.adxstudio.com/forums/adxstudio-portals/45235e5d-fd0c-e511-80fa-00155dc0a3d4
Issue 2 : ACS Endpoint Issue
An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier 'https://*******.crm.dynamics.com/' was not found.
Trace ID: 78613603-34e2-4f5c-8da2-139f3188cc73
Timestamp: 2016-12-14 17:17:54Z.
Resolution :
You can have a look my this post to resolve this issue.
Issue 3 : DLLs Compatibility Issue
The Organization Service URL is invalid. Metadata contains a reference that cannot be resolved: 'https://instancename.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0'. There is an error in XML document (1, 1298). The maximum nametable character count quota (16384) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing - long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 1298.
Resolution :
This can be solved by replacing both the Microsoft.Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll with the Dyamics 365 SDK, changing the MasterPortal project to .NET Framework 4.5.2 and adding the following dependent assembly references in Adxstudio VS solution's web.config file.
Issue 4 : If you have Subgrids on Entity Forms and you have enabled 'Edit' options to edit the subgrid records, you might face this issue :
Cannot create and populate list type Microsoft.Xrm.Sdk.KeyAttributeCollection. Path 'EditActionLink.EntityForm.KeyAttributes', line 1, position 2877.
Resolution :
Microsoft has been notified and aware of the issue. We are working with them to see what resolution options are available.
Unless we get the resolution of this issue from Microsoft, we can use below workaround to continue:
> If you are aware of Subgrid Configuration inside Entity Forms, you usually have three options (Entity Form, Webpage and URL) to open Subgrids records in Edit mode
If you choose Entity Form option to open the subgrid record in Edit mode, you will face the above issue, so recommend to use Webpage/URL options instead of Entity Form if possible.
So these are the known issues that you might face while upgrading your CRM instance to Dynamics 365. Hope this post help someone.
Do not forget to provide your suggestions and feedback.
But Hold On, Not all well for those who are using ADXStudio Portals for Dynamics 365.
or
If you have ADXStudio Portal integrated with your CRM instance and you are planning to upgrade it to Dynamics 365.
Today i would like to give some information about the ADXStudio Portal issues that you might face while upgrading your CRM instance to Dynamics 365.
Issue 1 : If you have exposed CRM Activity form (phonecall, email, task, any custom activity etc) on Portal as Entity Form, you might face this issue :
Server Error in ‘/’ Application.
A saved query for entity “interactionforemail” with the querytype “64” and isdefault “True” could not be found.
…
Exception Details: System.ApplicationException: A saved query for entity “entitlement” with the querytype “64” and isdefault “True” could not be found.
Resolution :
As per the ADX Community, This issue is due to use of OOB Activity Regarding field on Portal Entity Form.To get around this issue you will need to remove the “regarding” field from the form. If you need to assign a value you might use a workflow. We are looking into ways of supporting this field for a future release.
https://community.adxstudio.com/forums/adxstudio-portals/45235e5d-fd0c-e511-80fa-00155dc0a3d4
Issue 2 : ACS Endpoint Issue
An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier 'https://*******.crm.dynamics.com/' was not found.
Trace ID: 78613603-34e2-4f5c-8da2-139f3188cc73
Timestamp: 2016-12-14 17:17:54Z.
Resolution :
You can have a look my this post to resolve this issue.
Issue 3 : DLLs Compatibility Issue
The Organization Service URL is invalid. Metadata contains a reference that cannot be resolved: 'https://instancename.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl=wsdl0'. There is an error in XML document (1, 1298). The maximum nametable character count quota (16384) has been exceeded while reading XML data. The nametable is a data structure used to store strings encountered during XML processing - long XML documents with non-repeating element names, attribute names and attribute values may trigger this quota. This quota may be increased by changing the MaxNameTableCharCount property on the XmlDictionaryReaderQuotas object used when creating the XML reader. Line 1, position 1298.
Resolution :
This can be solved by replacing both the Microsoft.Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll with the Dyamics 365 SDK, changing the MasterPortal project to .NET Framework 4.5.2 and adding the following dependent assembly references in Adxstudio VS solution's web.config file.
<dependentAssembly> <assemblyIdentity name="Microsoft.Xrm.Sdk" publicKeyToken="31bf3856ad364e35" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0"/></dependentAssembly><dependentAssembly> <assemblyIdentity name="Microsoft.Crm.Sdk.Proxy" publicKeyToken="31bf3856ad364e35" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0"/></dependentAssembly>Issue 4 : If you have Subgrids on Entity Forms and you have enabled 'Edit' options to edit the subgrid records, you might face this issue :
Cannot create and populate list type Microsoft.Xrm.Sdk.KeyAttributeCollection. Path 'EditActionLink.EntityForm.KeyAttributes', line 1, position 2877.
Resolution :
Microsoft has been notified and aware of the issue. We are working with them to see what resolution options are available.
Unless we get the resolution of this issue from Microsoft, we can use below workaround to continue:
> If you are aware of Subgrid Configuration inside Entity Forms, you usually have three options (Entity Form, Webpage and URL) to open Subgrids records in Edit mode
If you choose Entity Form option to open the subgrid record in Edit mode, you will face the above issue, so recommend to use Webpage/URL options instead of Entity Form if possible.
So these are the known issues that you might face while upgrading your CRM instance to Dynamics 365. Hope this post help someone.
Do not forget to provide your suggestions and feedback.
