Microsoft has release CRM SDK 6.1.2 which fixes compatibility between Adxstudio Portals v7 and Dynamics 365! Read more here.
With all the changes in Dynamics 365 there are updates in the SDK and service that now make Adxstudio Portal v7.x incompatible. Outlined below are some of the issues you may run into, with some temporary workarounds if you want use Dynamics 365, and the potential pitfalls of these current solutions. As a result of the current status of support with Dynamics 365, it would be recommended that if you have an Adxstudio Portals v7.x implementation using CRM Online that you currently do not upgrade past CRM 2016 Update 1.
It looks like a fix is going to be coming soon! Posted over at the Dynamics 365 Team Blog about SDK backwards compatibility a new CRM 2013 SDK version that supports the new authentication will be released as SDK v6.1.2. With this updated SDK version you would be able to swap the reference DLLs in Adxstudio Portals v7 without the negative impact to functionality that switching to v8.2 SDK has. No date was provided for this update, but we may also see v7.0.0024 released with this fix in the new year.
One of the changes that is causing some issues is that the ACS endpoint is no longer being provisioned on online instances. This started with some CRM 2016 Update 1 instances but now seems to be rolling out more broadly. You might receive the following error when attempting to have your portal connect to the CRM.
ACS10002: An error occurred while processing the SOAP body. ACS50000: There was an error issuing a token. ACS50001: Relying party with identifier ‘https://instancename.crm.dynamics.com/’
Some instances of this could be resolved by changing the instance URL which would potentially cause the ACS endpoint to be rebuilt, but not always. You could also log a ticket with Microsoft Support for them to restore the ACS endpoint to your instance.
Adxstudio Portals v7.x ships as a solution compatible with CRM 2013, 2015, and 2016. As such it ships with the CRM 2013 SDK DLLs (v6.0 SDK). With the release of Dynamics 365 and SDK v8.2 the CRM 2013 SDK DLLs are no longer compatible, and you actually need to upgrade to the v8.1 SDK DLLs to connect with a Dynamics 365 instance. If you do try to connect Adxstudio Portals with its default CRM SDK 6.0 DLLs then you would likely see the following error message:
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.
This can be solved by replacing both the Microsoft.Xrm.Sdk.dll and the Microsoft.Crm.Sdk.Proxy.dll with the versions from the v8.1 SDK, changing the MasterPortal project to .NET Framework 4.5.2 and adding the following dependent assembly references.
<dependentAssembly> <assemblyIdentity name="Microsoft.Xrm.Sdk" publicKeyToken="31bf3856ad364e35" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-184.108.40.206" newVersion="220.127.116.11"/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="Microsoft.Crm.Sdk.Proxy" publicKeyToken="31bf3856ad364e35" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-18.104.22.168" newVersion="22.214.171.124"/> </dependentAssembly>
However while this will solve your connection issue it will come with unknown issues to other Adxstudio components like Entity List
and the portals front-side editor. The change in SDK version does have impact on the portal functions due to the differences between SDK 6.0 (CRM 2013) and SDK 8.1 (CRM 2016 Update 1) and the dependencies the portal components have.
At this time it would probably be recommended if you have a Adxstudio Portals v7.x implementation using CRM Online that you do not upgrade past CRM 2016 Update 1. If you run into the ACS endpoint error explained above then open a support ticket with Microsoft Support and request that the ACS endpoint be restored. If you have already been upgraded, or want to use Dynamics 365 and still need Adxstudio Portals v7, then your best option is to do the DLL upgrade and try to work around the current issues with the reference change.
Note if you start a trial or demo with the intent on showing Adxstudio Portals you can change to a previous version with the following guide.
Microsoft has been notified and aware of the issue. We are working with them to see what resolution options are available. As more information on a potential update to resolve these issue becomes available from Microsoft I will update this post. Below is currently a running list of known issues using SDK 8.1 with Adxstudio Portals v7.0.0022, this is in no way a complete comprehensive list.
- Entity List – grid configuration Edit action – will not appear on entity list rendering for Target Types ‘Web Page’ and ‘Url’, if using Target Type ‘Entity Form’ will result in error:
Cannot create and populate list type Microsoft.Xrm.Sdk.KeyAttributeCollection. Path 'EditActionLink.EntityForm.KeyAttributes', line 1, position 2877.
- Entity List – grid configuration Details action – will cause error if using Target Type ‘Entity Form’ as indicated above
Front-side editor – ‘Object reference not set to an instance of an object’ when Creating a new web page, or editing a page, or editing a snippet, or modifying a web link set.
If you discover other issues please let me know through comments, Twitter, email or however else and I will update this listing.
Note: This post also appears on Adoxio Business Solutions Team Blog.