ArcherPoint Dynamics NAV Developer Digest - vol 215
The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.
As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media…so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.
Dynamics NAV Windows Client and C/AL is Going Away
Matt T: It’s official: Beginning in 2020, the Windows client and C/AL will be thrown on the bonfire…it’s the Web Client and AL only from that point on.
Matt S notes: “That is only 15 months away.”
Matt T states: “Probably 18 to 24 months, depending on whether it goes away with the May 2020 or October 2020 release.”
Tim L clarifies: “Azure, on premises, everything?”
Jon adds: “Of course, legacy will continue to limp along for several years, if not decades. In fact, most of our upgrades we’re getting now are from pre-RTC.”
Suresh replies with the Business Central Roadmap:
Kyle observes: “Note Suresh’s diagram and the push to CDS. I get what they are trying to accomplish, making a customer a customer and a contact a contact regardless of whether you are in Business Central, CRM, Flow…whatever Azure thing.”
Tom H notes: “If NAV 2020 is the last C/AL version, that means we should be done doing C/AL changes sometimes around 2034, when the last NAV 2.5 customer decides to upgrade. :)”
Matt T agrees: “Exactly. It’s a long-term shift. Right now, it’s 90% RTC and 10% Classic. Trends typically continue in this business. In 2028 it will be 90% AL, but there will still be that 10% lagging behind. Another thing of note is that Microsoft has converted the NAV W1 database completely to an Extension. While I still expect that everyone will be coding in AL subscribing to the events published by Microsoft, there is still the long-shot possibility that you could customize on-premises the same way you do today, just using AL instead of C/AL.”
Can You Create and Modify User Accounts in Dynamics NAV and Not Have Access to Financials?
Kyle asks: “Is it possible in modern NAV to grant the rights to create and modify user accounts, but not be able to do anything else in NAV, especially no access to financials? Our intent is to delegate account creation to an IT department help desk, but they do not get access to the company financials.”
Matt T answers: “No, because then they could just give themselves access or create a fake user and give that user access. You could technically build some wacky customization, but you definitely can’t do this out of the box.”
Kyle replies: “It won’t let you grant access that is more powerful than what your user has. But that having been said, it also means that if I don’t have access to financials, then I can’t grant *you* access to financials. So, your point is still valid. How do our customers handle this? Do they just live with the fact that their IT department has full NAV access?”
Matt T responds: “I always assumed they just live with it. I believe it is actually enforced that there is always at least one super user in the database once users have been setup, so someone has to have it. Perhaps tools like Easy Security or Fastpath could help, but I am not sure.”
If you are interested in NAV development, be sure to see our collection of NAV Development Blogs.