{"title":"Troubleshooting errors in OData/SOAP web services on pages, queries, and codeunits","url":"https://jonas-paprotka.de/docs/dev-itpro/webservices/web-service-troubleshooting-soap-odata-ui-pages/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/web-service-troubleshooting-soap-odata-ui-pages, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/web-service-troubleshooting-soap-odata-ui-pages","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about how to troubleshoot Business Central web service errors on OData/SOAP endpoints on pages, queries, and codeunits.","date":"2025-03-11","meta":{"topic":"troubleshooting-general"},"outline":[{"level":1,"title":"Troubleshooting errors in OData/SOAP web services on pages, queries, and codeunits","slug":"troubleshooting-errors-in-odatasoap-web-services-on-pages-queries-and-codeunits","at":0,"chars":1658},{"level":2,"title":"Don't use Microsoft pages as SOAP/OData APIs","slug":"dont-use-microsoft-pages-as-soapodata-apis","at":751,"chars":580},{"level":2,"title":"Related information","slug":"related-information","at":1331,"chars":327}],"text":"# Troubleshooting errors in OData/SOAP web services on pages, queries, and codeunits\nTroubleshooting web service errors can be tricky because the root cause of the error can be in multiple places:\n It can be in the client that's calling the web service.\n It can be related to the network between the client and the web service endpoint.\n It can be in the code behind the web service endpoint.\nFor errors occurring in the web service client or in the network, refer to the general troubleshooting guide Troubleshoot web service errors<web-service-troubleshooting>.\nIn 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.\n## Don't use Microsoft pages as SOAP/OData APIs\nThe 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.\nIf you require a stable API on a page in the Business Central application, you have two options:\n1. Take a copy of the source code for the page and host it in a per-tenant extension.\n2. Use the provided built-in APIs. See api-overview.\n## Related information\nHandling UI interaction in web service endpoints<handling-ui-interaction-when-working-with-web-services>\nweb-services-best-practices\nTroubleshoot web service errors<web-service-troubleshooting>\nweb-service-telemetry\n../developer/devenv-debugging#debugging-web-services\nWeb services overview<web-services>"}