web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Microsoft.Xrm.Client d...
Microsoft Dynamics CRM (Archived)

Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

(0) ShareShare
ReportReport
Posted on by Anne Pessoa 14

Hi,

We have an CRM 2016 (8.1.1) Online customer with ADX 7.0 and we got an alert from Microsoft about the Access Control Service (ACS) deprecation happening on the 30/06/2017. But they mention in the email this blog( https://blogs.msdn.microsoft.com/crm/2017/02/01/dynamics-365-sdk-backwards-compatibility )post that mentions the deprecation of  Microsoft.Xrm.Client.

They also mention this ADX blog (https://www.adoxio.com/blogs/team/2017-02-01-crm-sdk-612-released-fixes-adxstudio-and-dynamic/) post and this one doesn't mention the need of removing the  Microsoft.Xrm.Client, so we are not too sure if there's a need to remove the Microsoft.Xrm.Client and deal with all the errors or not, does anyone know about this? Should we only update the Microsoft.XRM.SDK in the ADX project and publish and we will be ok?

Thanks a lot!!

*This post is locked for comments

I have the same question (0)
  • Anne Pessoa Profile Picture
    Anne Pessoa 14 on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Hi, is anyone out there preparing for this ACS deprecation too?

  • Community Member Profile Picture
    Community Member on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Hi... We are planning to Move AAD authentication.

  • Suggested answer
    Guido Preite Profile Picture
    Guido Preite 54,084 Moderator on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Hi Anne,

    you just need to replace the SDK dll on your ADX Portal (to the version 6.1.2) as indicated inside the link, in order to make your 7.x Portal to still working after your CRM instance is updated to Dynamics 365

  • Anne Pessoa Profile Picture
    Anne Pessoa 14 on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Hi Guido,

    Thanks for getting back to me on this. Sorry if my following question doesn't apply, I'm not an expert on ADX, but our ADX solution use of the Microsoft.Xrm.Client a lot, should we be worried about this? We are not upgrading to Dynamics 365 now, just worried about the ACS change Microsoft will apply to their Servers on the 30/06

    Thanks again!

  • Suggested answer
    Guido Preite Profile Picture
    Guido Preite 54,084 Moderator on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    you have two problems:

    1) you have an ADX 7.x Portal with a CRM Online instance and sooner or later you will be forced to upgrade to Dynamics 365, so you need to change the SDK dll used inside the portal to version 6.1.2 to make sure it will continue to work.

    2) if you have code (like web applications or console applications) using Xrm.Client (apart from the portal) then you can start to update the code to use Xrm.Tooling

  • Anne Pessoa Profile Picture
    Anne Pessoa 14 on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Thanks again Guido.

    We are looking into removing the XRM.Client for the Dynamics 365 upgrade in a latter date, as at this point we will be able to apply this in DEV first and then work from there to make sure ADX is working.

    Our concern here is that we can't apply this Microsoft change about the ACS on DEV before the 30/06 to make sure we have everything fixed, so we want to make sure we have everything covered to avoid any surprises on the 01/07 (day after the change).

    Removing the Microsoft.Xrm.Client generates loads of errors in our ADX solution.. If we just add the Microsoft.Xrm.Tooling.Connector and use the CrmServiceClient to connect to CRM, and keep using the Microsoft.Xrm.Client for other actions like caching (Microsoft.Xrm.Client.Caching.ObjectCacheManager) or GetRelatedEntities, will we be ok on ADX?

    The version 6.1.2 mentioned in the ADX blog post still includes the old Xrm.Client and just updates the others.

  • Verified answer
    Guido Preite Profile Picture
    Guido Preite 54,084 Moderator on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    As I wrote before, you can start to update your other code (APART from the portal) to Xrm.Tooling, for the Portal for now you just need to update the SDK files with the one from 6.1.2

  • Anne Pessoa Profile Picture
    Anne Pessoa 14 on at
    RE: Microsoft.Xrm.Client deprecation ADX Studio on 30/06/2017

    Thanks!!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

#3
ED-30091530-0 Profile Picture

ED-30091530-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans