If you are a developer or consultant who works for a modern Business Central-project that includes the integration of 3rd party services – you might come across this error while using HttpClient. Find out in this article why it happens, what do to about it and in which situation you have to live with it.
Those of us that have been around long enough will remember that Microsoft Business Solutions-Navision 4.0 came out with the new XMLport and MenuSuite object types. I can clearly remember a sort of astonishment about this UI-less XMLport. To allow you to feed this “pipeline” with data you had to wrap it in another object
Default reports of Microsoft Dynamics NAV will save the request page values and allow the user to modify them in the next run of the report. However when a developer develop a new report it will not save the last run value of the request page. I saw few threads in the Dynamics NAV community forum regarding this.
The user interface of the XMLport has always been somewhat of a black swan. On the classic platform it was absent and you had to work around it yourself. With the emerge of the windows client (RTC) we did get a request page as one of the incentives for us to start adopting the 3-tier technology.