Skip to main content
Submitted by Suzanne Scanlan on 5 June 2020

ArcherPoint Dynamics NAV / Business Central Developer Digest - Vol 296

ArcherPoint Dynamics NAV and BC Developer Digest Blog

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.

Using Code Cop with AL Development

Kyle polls the tribe: “So, honesty question for my AL peeps. Do you actually do all of your coding with the Code Cop fully engaged?”

Matt T affirms: “Yes, we just got used to it in the IP group. There are too many things that Microsoft kicks back on AppSource submission if you don't. It’s easy to fall into habits we're used to, like changing field names, that we're not allowed to do anymore. You just pass defects down the line if you don't have it turned on.”

Kyle continues his query: “So you mean to tell me that you went through your code and changed this:
 
RespCenterCode := UserRespCenter.LookupResponsibilityCenter(UserId()) 

to this:
 
RespCenterCode := UserRespCenter.LookupResponsibilityCenter(CopyStr(UserId(), 1, 50)) 

just in case UserID ever becomes longer than 50 characters long?
  
Possible overflow assigning Text to Code[50] AA0139”

Matt T replies: “In short, yes. Takes 10 seconds to fix.”

Tom H adds: “It probably helped that you weren't converting 20-year-old crappy code from NAV 1.2.”

Matt T adds: “For our Rental Process Management app, we (and by that I mean mostly Len) were converting a C/AL solution. There were points where we had thousands of warnings, maybe even a point where we had a little over 10,000. But it was a quality decision that we made. We consciously prioritized robustness (the degree to which the system continues to function under invalid inputs).”

Tom H acquiesces: “I stand corrected.”

Trigger Codeunits in Dynamics 365 Business Central Version 16

Kyle informs: “I'm sure you are familiar with the 20 million object ID tables. With BC16, they have now added codeunits up in the 20 million range. They are called things like Global Triggers, Version Triggers—all of them are trigger codeunits of some kind.” 

Decoupling Business Central – and a Call to Action

MVP Mark Brummel worked on a project last year with Microsoft to decouple functional areas from the base BC application, as reported in a previous Developer Digest blog. We finally have the outcome of that project and a call to action for partners to request new interfaces. Read all about it in Mark’s Breaking Up the Base App | Request New Interfaces post.

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.

Blog tags