/XRMServices/2011/Organization.svc* → endpoint removal
Microsoft Dynamics 365 Web API
Deprecated, no date
Microsoft has deprecated the Organization service SOAP endpoint without a shutdown date. This change affects requests to /XRMServices/2011/Organization.svc*. While the endpoint continues to work and receive support for now, calls to it will eventually fail once it is removed.
Calls it hits
/XRMServices/2011/Organization.svc*
What to use instead of these calls
Use the Web API equivalent operation under /api/data/v9.2/, or an updated SDK for .NET using Microsoft.PowerPlatform.Dataverse.Client.
In Microsoft Dynamics 365 Web API's words
Microsoft introduced the Organization service endpoint, known as the SOAP endpoint, in 2011. This endpoint is deprecated. This means that it continues to work and be supported until Microsoft removes it.
Facts
- API
- Microsoft Dynamics 365 Web API
*.crm.dynamics.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Microsoft Dynamics 365 Web API's own pages
Questions
When does this change take effect?
Microsoft Dynamics 365 Web API deprecated /XRMServices/2011/Organization.svc* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Microsoft Dynamics 365 Web API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Microsoft Dynamics 365 Web API 1
-
No date
/XRMServices/2011/OrganizationData.svc*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.