ArcherPoint Dynamics NAV Developer Digest – vol 73

As they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s 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 group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.

Per Mogensen commenting on the security features of Dynamics NAV 2016:

We asked Per Mogensen of Mergetool to explain the differences between new NAV 2016 capabilities and Easy Security, as there appears to be some overlap. Here is Per's response:

“The features for security of NAV 2016 is similar to our Light Product with a registration key added for recording of TableData permissions. The recording of permissions is not 100% correct for all the data read, but is it getting pretty close. Microsoft also has the grouping of Permission Sets, but it is done a little different than in our solution.

“No additional Permission Sets or help with designing security for Segregation of Duties are in the solution so the customer has to start designing proper security. Object Level Security, Quick Security, Expiry, Field Level and Data Security is not in the added features in NAV 2016.”

Question on implementing a cash basis company in NAV:

Question: Has anyone implemented a cash basis company in NAV and dealt with having to modify the sales taxes collected report to calculate taxes due based on payments received, not sales tax amount accrued?

Dan Sass: This is standard functionality in NAV. Look at the unrealized sales tax functionality for jurisdictions. I have used before and t works fine.

Alan Campbell shared an article comparing Risk and Uncertainty:

When viewing projects, the terms “uncertainty” and “risk” are often used interchangeably. This article, however, demonstrates a clear difference between the two: Uncertainty is the chance that something will happen, risk reflects how that uncertain outcome will cause harm. So risk is only important when an individual stands to gain or lose something based on an uncertain outcome and is subjective to the person taking the risk.

Read the article: Risk Is in the Eye of the Beholder

Reader questions and comments:

Last week, our Developer Digest vol 72  received a question from a reader. In discussing upgrading from Classic reports to RDLC, it was stated that default settings can be changed for Visual Studio to adjust the default font and text box height. A reader asked, "How can the default font, font size, textbox height, etc.be defined?"

With thanks to our own Saurav Dhyani, that process is outlined in more detail. See his blog, Dynamics NAV Role Tailored Client - Master Template for Report Layouts for more on this topic.

If you are interested in NAV development, check out our collection of NAV Development Blogs.

For step-by-step instructions on how to perform specific tasks in Microsoft Dynamics NAV, see our collection of How-To blogs.

If you found this post useful, you might also be interested to read through our archive of the Dynamics NAV Developer Digest.