Handling exceptions inside NAV when using Web Services integration

In a forum post I’ve recently received a request on how to handle a scenario like the following: an external client application has to call a Microsoft Dynamics NAV object (codeunit) published as Web Service. The codeunit receives input data from the external application and then performs some operations on NAV (the business logic is managed by NAV itself). If something wrong happens on the NAV transaction (error), NAV must be able to log the incoming request and the error that the request has... Read the full text.
Comment List