Announcements
Hi Community ,As a part of Odata Deprecation Official Blog , we are upgrading our CRM service connection C# code with IOrganizationService and CrmServiceClient that inherits from the Microsoft.Xrm.SDK (part of Microsoft.CrmSdk.CoreAssemblies DLL)We see the Microsoft.CrmSdk.CoreAssemblies latest version (v 9.0.2.49) also have the endpoint referencing the Organizationdata.svc endpoint . Will this cause any issue post the v2 deprecation . I am attaching the old code and upgraded C# code (without use of organizationdata.svc endpoint) that makes connection to the CRM service . Could you please check and confirm us on this. And also if you suggest any other good approach also is appreciable . Thanks in advance
Click referred for Code Upgradation - Connect CrmServiceClient
the code you posted is not strictly related to the OData 2.0 endpoint but is important for other parts (deprecation of OrganizationServiceProxy)
in your updated code, just return the conn object (containing the ServiceClient object you created), you don't need the line where you check the OrganizationServiceProxy
Thank you very much for the reply . Let me explain by point here
The code you posted is not strictly related to the OData 2.0 endpoint but is important for other parts (deprecation of OrganizationServiceProxy) - In the official blog wherever we make connection with use of OrganizationData.svc , they ask us to replace (In our case we have CrmServiceUrl used) . Please correct me If I am wrong .In your updated code, just return the conn object (containing the ServiceClient object you created), you don't need the line where you check the OrganizationServiceProxy - I tried the same as well but I am getting the CrmConnectOrgUri and other properties connected with Organizationdata.svc . Here is where I am little confused like whether it cause any issue post the Organizationdata.svc deprecation. attaching the snaps here. Once again , thanks a lot for your prompt response.
your old connection uses organizationdata.svc but that is a very very old way to connect, I never used it as a CrmServiceClient with the connection string is enough (CrmServiceClient is the object of the .NET framework SDK, ServiceClient of the new .NET SDK)
the screenshots you posted refers to organization.svc, not organizationdata.svc, also when you use the official SDK you are "protected" from these changes, if tomorrow under the hood they change the .svc endpoint your code is not affected (because now you are using a connection string)
Great .Now I am clear . Thank you very much
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.
Jump in, show your community spirit, and win prizes!
Expanding mentorship, skilling, and AI innovation
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Valantis 414
WarrenBelz 377 Most Valuable Professional
Kalathiya 315 Super User 2026 Season 1
