Improvement Idea #14:
We love Business Central,
but a lot Role Centers deserve a little more of love. This for example is the current Service Role Center:


Improvement Idea #14:
We love Business Central,
but a lot Role Centers deserve a little more of love. This for example is the current Service Role Center:


Improvement Idea #13:
We love Business Central,
but let’s get real, 80 GB Database Limit for the Cloud Database is just too little for any real businesses. Make it 5 or 10 TB and think how to monetize every addition 500 GB after the first 500.

Improvement Idea #12:
We love Business Central,
but we really really hate the XLIFF Integration in Visual Studio Code. First you need to have one or more 3th-Party Extensions to even get started. Not only that, but if you refactor Objects, Fields, Elements or Label – because Microsoft like to see Prefix or Suffix for its AppSource Apps – you lose the translations. You can rename every element in the extension, but this does not apply to XLIFF in anyway. Why is that exactly?

Improvement Idea #11:
We love Business Central and the Power Platform,
but it is sad to see that you can only use Power Automate (former Flow) Workflows, Power Apps or Power BI App with the tables and fields of the exposed standard API instead of all tables and fields even with addition extensions.

Improvement Idea #10:
We love the Business Central staff,
but the Business Central guys are understaffed. Looking at the past 10 years of product quality, it safe to assume that there is not enough Business Central staff that takes care of proper Quality Assurance both in the Platform and the Application. If you don’t believe us, just take a look the Cumlative Update release notes.
Very annoying breaking bugs of this week:
Also there are certainly no employees who translate the documentation into other languages (probably rather Bing Translate).

Improvement Idea #9:
We love Business Central,
but why are there so many artifacts in the Base App like DotNet-Variables for Xml instead of the new native Xml Data Types or RunOnClient-Attributes?

Improvement Idea #8:
We love Business Central and Visual Studio Code,
but you can’t you just open the Report Layout Files (.rdlc) in the Report Builder and change the layout?

Improvement Idea #7
We love Business Central,
but imaging you build with sweat and tiers a genus AppSource App for Business Central. Now you also need to be an expert in payment portals and implement that yourself, because one of the biggest software company in the world forgot to include a payment options into their highly strategic Dynamics 365 AppSource. Why?

Improvement Idea #6:
We love Business Central,
but why can’t you debug a Cloud Sandbox. Imaging you have a customer in the cloud and he/she gets an error message. You can’t just attach to debug, because Microsoft don’t want you to.


Improvement Idea #5
We love Business Central,
but since the first Navision Application Server (NAS) to the Job Queue in NAV 2013 and the Task Scheduler logic since NAV 2017 (till today), there were so many instances where background automation would just sudden stop working and there seems to be not watchdog or self healing in place. You still have to set the Job Queue Entries on Status Wait and then Ready, if you currently what to get a died Job Queue Entry up and ready.
