Apparently, the PowerBI connector is adding the header Data-Access-Intent: ReadOnly to requests when loading data from Business Central. While this is a good practice in general for GET requests, you may run into an error message with the sales APIs. This applies to salesQuotes, salesOrders and salesInvoices.
While there are different ways and tools to handle the issue, in this post we will use a Microsoft standard extensions for DevOps to resolve merge conflicts within Azure DevOps. The extension is called “Azure DevOps Pull Request Merge Conflicts” and is available in the marketplace (free).
With the Performance Toolkit you can test your performance inside Business Central. But in the modern world Business Central is not on his own. There are dozens of interactions with other systems. And you want to test that also for your performance. Well that is also possible with the Performance Toolkit! In this blog I will show you:
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