Through the page 9521 Database Missing Indexes it is possible to see the missing indexes suggested by SQL Server for Business Central (in fact, an SQL function is called which returns the missing indexes).
In this case the same function has been recreated on SQL (stored procedure) so that it can be launched both from BC (Onpremise) and from SQL.
We always try to upgrade all customers to latest release – and we encountered some delays in API communications, which seemed to got worse at every new upgrade. At some point, every API call took from 500 to 1000 milliseconds. I think we all agree that this is FAR to high. Even for a simple call, like getting the companies, it took so long.
As you probably have noticed, once you upgrade your extension from previous Business Central versions to BC20, their various errors should appear that need to be refactored. So in this article, I will present the most common cases and how to rework them when you upgrade the extension to the Business Central 20 OnPrem version.
I got an internal question from our consultants on how they are able to access the license information of the customer for an OnPrem customer. There are a few scenarios where that’s interesting. Just to check which license is in production. Or how many objects or users did they buy. Well – anything license wise ;-).
It seems that lately, I’m only able to blog about something when I have a tool to share.. . That needs to change .. :-/. But not today. Today, I’m going to share yet another tool that we at the ALOps-team have been working on to serve many of our customers. And we decided to share it with the community. The tool is free, it will stay free … but, there is a …
Yesterday we stuck with an issue for a customer which we recently upgraded to Business Central 13.x on-prem. It took time to find the solution so I thought to share a solution with everyone.
Issue Description – Report using custom Barcode Font does not work with Web client but works with the windows client.