Microsoft Dynamics 365 Business Central: What's needed next
It's just six months since I wrote to explain what this product codenamed Tenerife was. Its seems like a lifetime ago. Just days later it officially became Microsoft Dynamics 365 Business Central, MSDyn365BC or BC for short. And just a month later, on April 2nd, it was available in the first markets.
More questions than a preschool.
Questions have dominated that six months. Just this morning I met someone from a fellow partner firm here in the UK who hardly said hello before he asked, "How are you getting on with Business Central?" I left that meeting, checked my email to find another partner asking, "Do you have or know a solution for this which works with BC right now? We really need it." Even on my own team there is a constant stream of ‘we used to do this with NAV, how/when can we do the same with BC?' discussions.
Very little is ‘known for certain' any more
I don't think I realised how much Dynamics NAV was a comfortable place to be. Most of what we were asked to deliver was, at worst, a variation of something we'd done many times before. Pushing the envelope wasn't about whether it would work or not, but if we could do it in the timescales the prospect asked for.
BC is a different place with its new platform, new development environment, new restrictions, and new best practises. Then to top it off, for most of us used to the Windows client ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here