My Dynamics 365 Business Central’s priorities for Microsoft in 2022

I was quite shocked this week when someone asked why I didn’t make a 2022 version of my priorities for 2021 and 2020 for Microsoft. Then, when two separate people from Microsoft mentioned it, I decided it was better to do it.

I fix this in my hotel room at the end of the Days of Scandinavian Knowledge. Six hundred or more people in two days seem to agree that Microsoft Dynamics 365 Business Central is in a pretty good place right now. Many of the blockers that prevented the adoption of SaaS have disappeared. The projects are going smoothly, the modernization of the inherited versions is a faster bullet speed than the diesel maneuver, in general our world is as good as I remember.

When I try to share my uncolored opinions in an article, I’m never sure if people think, “Xx, James’s getting one again.” The idea is that this year I should write a list for the partner community, not for Microsoft. In fact, most of today’s problems are focused on the channel, and progress often seems slow. I guess the main problem is the lack of skills among partner teams, combined with the inability to invest enough time not only in learning, but also in adapting the modern set of tools built by Microsoft. I find it ironic that after years of complaining that we have a bad relationship compared to our cousins ​​in C #, JavaScript and even PHP, when this toolkit catches up, for example with the beautiful CI / CD capability, then you won’t use much it (yes, JRM, I think of you!), although Microsoft simplifies it to the level of GitHub and go.

Don’t be fooled into thinking that I have no working elements in my work for Microsoft. The fact that we currently have bigger problems on our side of the fence does not mean that they cannot break.

So let’s list this…

    1. Improvements in the basic application. Yes, I know you’ve done a lot of the BCIdea questions, but as I said, the ones that get the most votes don’t actually stretch the boundaries very far, do they?

      But please be careful to go the other way and, say, process all the sales and purchase documents. This approach would break so much, not only for ISVs, but for customers as well. In fact, I would say that the aim should not be to give up, but to give priority to what I could describe as filling in the gaps over what exists now.

      This means looking at the functionality that custom tenant extensions constantly “fill”. You’ll also find a bunch of apps in AppSource, because all the mature partners have responded to the feedback and created their own “gap-filling apps” a long time ago. All this adds to the cost of implementation. More importantly, the new partners do not know how to respond to complaints, instead concluding that the main application is not good enough.

      Do you want an example? SharePoint integration (sorry, Eric); drag and drop the SharePoint object store to be accurate. You gave it away in 2013, even though it was from a third party. This is a basic expectation for every customer, so we all use our own or a third party every time.

      The comments are different, valued by customers, but I’m puzzled by what your strategy is these days. What I know is a basic text line of limited characters without word transfer, not good enough. Even Waldo (obviously trying to upset all my friends) invented his WaldoPad three years ago, Euro AJ tells me.

      How about some improvements in sales and purchase documents, such as the ability to convert some lines from an offer to an order, not all. I am sure that your telemetry will confirm that the sales documents in particular are one of the MOST USED parts of the system. And yet, when was the last time you had love?

    2. On the other hand, some of me want new additional functionality. Please, something shiny and new, not another refactoring or connection between two existing bits. But don’t be too ambitious here, you don’t have to invent an entirely new book or production process, for example.Following the topic of improving order processing, how about adding a subscription document that allows us to create repeat orders in the same way that a recurring journal creates a journal. One of your developers suggested testing this extensible Enum, which you use for a document type, but I declined. Why don’t you give it and prove the thesis?

      I know there are a few ISVs that have subscription solutions, but if they are good and true professionals, their product will be much more advanced than what you have invested. In fact, there is an argument that you provide a base to validate their product and expand the market for them.

    3. Stop downloading apps for the next three editions. We all work seamlessly to migrate legacy NAV systems to SaaS, and the more you reject, the harder it is because refactoring takes place. Give us a little space to break the gap from C / AL to AL before heading the mountain even further.The logical moment to start the withdrawal again (and I know they are needed and will come) is when BC14 goes out of maintenance. Then officially you only have to think about BCCurrent, as we call it. Until then, let’s take as much with us as possible, keeping the delta of functionality between BC14 and BCCurrent as small as possible.

      And can I insert 3.1 here? Can you open the feature management for ISV, please? We have the same challenges and there is no point in creating our own equivalent.

    4. User-defined query tool. Yes, another that was a previous question but didn’t seem to come up. This would allow so many improvements for so many areas that I believe it will become one of the most widely used tools in the system. Power BI, custom tiles for central roles, custom APIs without code, this is just the beginning.

Leave a Comment

Your email address will not be published.