ArcherPoint Dynamics NAV Business Central Developer Digest - vol 327
December 2020 cumulative updates, the impact of Table extensions on performance, and 1099 complications are topics in this edition of Developer Digest.
The Dynamics NAV and Business Central 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/BC experts and devotees around the world. We hope these insights will benefit you, too.
Microsoft Dynamics NAV and Business Central Cumulative Updates from December 2020
See the links below for details about the December 2020 cumulative updates for Dynamics NAV and Business Central:
- Dynamics 365 Business Central 2020 Wave 2 (Update 17.2)
- Dynamics 365 Business Central 2020 Wave 1 (Update 16.8)
- Dynamics 365 Business Central April 19 On-Premises (Update 19)
- Dynamics NAV 2018 (Update 36)
- Dynamics NAV 2017 (Update 49)
- Dynamics NAV 2016 (Update 62)
The Impact of Table Extensions on Performance
We all know that when you’re working in Dynamics 365 Business Central, Table extensions can take a toll on performance. But Stefano Demiliani wanted to know just how big that impact is. Learn what he discovered in his post, Dynamics 365 Business Central: The Impact of Table Extensions.
1099 Reporting for 2020 Tax Year Will Be an Extensive Endeavor
Kyle advises: “Do not underestimate the amount of effort it is going to take to do 1099s for 2020. I did a comparison of BC 16.5 to BC 16.8, and there are 22 base objects that are either changed or added for 1099 reports. I have the choice of applying the cumulative update (easy for me, hard for customer) or pulling all this out into custom objects (hard for me, easy for customer, bad for future upgrades). This is big:
local procedure UpdateIRS1099FormBoxesTo2020()
InsertIRS1099(‘MISC-14’, ‘Nonqualified deferred compensation’, 0);
Saurav agrees: “True, but I think we need to upgrade them to BC 16.8. It should not be hard for the customer; what if they were on BC SaaS? They would have been upgraded to latest one without notice.”
Kyle responds: “The Upgrade codeunit provided with the cumulative update does not have date filtering. So, when it changes all MISC-07 to NEC-01, it does not filter the dates for the vendor ledger entries or posted purchase invoices. I just ran that on a beefy 16.8 on premises server, and the process took 45 minutes. This is just my opinion, but I think you should copy that codeunit to a new custom codeunit and add date filtering before using it on a customer database.”
This sparked additional conversation with the outcome being that a support ticket has been submitted to Microsoft about the issue, as well as more discussion around what years this change will impact:
Jon asks: “If the update only majorly affects the 2020 1099 submission, what are the previous year’s ramifications?”
Kyle replies: “Previous years will get broken as the 1099 code stands right now. The update code will change every MISC-07 to NEC-01, even for 2019 and on into the past. Every vendor ledger entry. I don’t know that a customer would need to reprint past year 1099s, but this update will break their ability to do so.”
More to come on this topic as more information comes available.
Excitement—and a Warning—About New Email Features in BC 17
David Kolenko is excited about the “Awesome new email features in BC 17!”
Saurav warns: “Only switch to the new email if the customer has no ISVs that are still dependent on an old SMTP email module. If there are PTEs dependent on old SMTP, those will be required to be redeveloped.”
Developer Tip of the Day: ObjectId
Kyle shares this tip: “You can now get a Page or a Report to tell you what its name and object number are in AL without having to look it up in the AllObjWithCaption table.
Report.ObjectId(true) gets you the name
Page.ObjectId(false) gets you the object number
If you are interested in Dynamics NAV and Business Central development, be sure to see our collection of NAV/BC Development Blogs.
Read the “How To” blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.