Troubleshooting errors in OData/SOAP web services on pages, queries, and codeunits.
Troubleshooting web service errors can be tricky because the root cause of the error can be in multiple places:
- It can be in the client that's calling the web service.
- It can be related to the network between the client and the web service endpoint.
- It can be in the code behind the web service endpoint.
For errors occurring in the web service client or in the network, please see the general troubleshooting guide Troubleshoot web service errors
In this article, you can learn more about different methods and tools that you can use for troubleshooting web service errors on OData/SOAP web services on pages, queries, and codeunits.
Don't use Microsoft pages as SOAP/OData APIs
The Business Central application evolves over time and changes happen to the user interface as part of this. This means that the page structure and fields might also change when interacting with the page from a web service client and it is not something you can depend on being stable over time.
If you require a stable API on a page in the Business Central application, you have two options:
- Take a copy of the source code for the page and host it in a per-tenant extension.
- use the provided built-in APIs. For more information about APIs, see API overview.
Related information
Handling UI interaction in web service endpoints
Web Services best practices
Troubleshoot web service errors
Web service telemetry
Debugging web services
Web services overview