The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Check out the latest Business Central updates!Learn about the key capabilities and features of Dynamics 365 Business Central and experience some of the new features.
Download overview guide | Watch Business Central video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
With Business Central and the change from CAL to AL a lot of expected and unexpected obstacles have crossed our paths, wether you are a salesperson, a developer or a decision maker. I recently found out what the biggest obstacle to transition to Business Central can be.
I spend a good chunk of time developing in BC and NAV, and while it is true there is a lot to learn in regards to the developing side (AL syntax, VSCode, DevOps, translation tools, CAL to AL converters, new development patterns and so on), sometimes we can forget there is also a lot of functional improvements and changes. This is specially notorious when you have a SaaS customer, where you see new buttons and options constantly popping up out of nowhere.
A few days ago two colleagues talking about a problem in a BC extension, and I noticed the base of their solution was flawed, and hence the source of their problems. When that was pointed out it appeared to have no effect and they kept on focusing on solving the symptoms and not the root cause. The reason was not because fixing the root problem was harder, it just involved touching some new tools they were not familiar with. And that’s when it hit me.
I do not mind pointing out what Microsoft does wrong, but this time they are taking both the information on screen for the user to see and the documentation both functional and technical to the next level. There is an incredible amount of information to consume, both from official sources and from other bloggers. It’s overwhelming. Big shout out to Microft Learn, that site is amazing, and once they finish adding up everything that’s missing it will be incredible.
Just like a marathon, even if your body can keep up, your thoughts might betray you. And this brings up an interesting debate, where a lot of us are self-teaching ourselves based on what’s online and sometimes with help of others, but I struggle with knowing exactly whose responsibility it is to keep us updated in our companies.
It is clear to me that I will benefit from everything I learn and know, but is it our companies responsibility to invest time and money into helping their workforce update their knowledge and skillset with the new tools and patterns? Or does that fall entirely onto the worker?
If you are a developer, a consultant or a decision maker please let me know what you think below, I am very interested in your opinion.
La entrada A partner’s biggest obstacle transitioning to Business Central? se publicó primero en José Castro's blog.
Business Applications communities