Skip to content

ArcherPoint Dynamics NAV Developer Digest - vol 72

ArcherPoint’s technical staff pose questions, find answers, and share new discoveries about Microsoft Dynamics NAVAs 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.

Matt Traxinger on the new Try / Catch functionality in Dynamics NAV 2016:

NAV 2016 has new development functionality to do Try / Catch. Basically what that means is you can write your code to Try to do something, and if that code throws an error instead of displaying the error it will return control back through the call stack to where the function was called so you can handle the error in your own way. It looks something like this:


Now think about this:

IF NOT PostMyOrderThroughCodeunit80 THEN BEGIN
MESSAGE('Could not post order.');

What do you think the results would be if there was an error towards the end of Codeunit 80? :)

Suresh Kulla: Try Functions does not roll back the transaction, this is not a true Try/Catch as you see in .NET, personally i stay away from this new function.

Matt Traxinger: Exactly. I am currently in deep thought on this :). If an error happens in a try function, did it really happen?

Should we not use it because it can be misused? I don't know that I'm ready to go that far.

By the way, the correct way to do this is:

IF NOT Any_Function_That_Performs_A_Database_Transaction THEN BEGIN
ERROR('My custom error.');

Left to the student as an exercise: What will happen if there is a COMMIT statement in the function, how do we rollback?

Saravanan Shanmugam on upgrading reports from Classic to RDLC:

When Upgrading Reports from Classic to RDLC you would have faced font related issues. The reason is "Helvetica" font is obsolete in RDLC and what we can see a close match in RDLC is "Segoe UI". The default font for visual studio is "Arial", so in future if any other developer wants to bring any text box it would be in "Arial", so the developer should keep an eye on the font that the report currently used. One more findings which we got today is in classic report the textbox height is "423" where we upgrade the report we use "0.423CM" it is fine there but you would see the letters getting shaved off at bottom for the below letters " g,q,y,p". so we have tried possible values between 0.423CM to 0.486CM and here the solution is "0.486CM" this is the least value where we can fix the issue.
Note: In PDF it will look fine.You will not see this issue unless you print the report in paper.

Faithie Robertson: Great solution! The text box height issue with letter tails being cut off has come up several times lately. Could the default font and text box height be put into the default settings for Visual Studio? (Which admittedly, I have not yet tried but need to.)

Saurav Dhyani: Yes, we can set it on the default settings.

Alan Campbell shared a video on Agile Product Ownership in a Nutshell:

This is a great video that provides a quick overview of the role of the product owner and the overall agile process. This is really targeted toward the software development community, but the strategy and principles are identical to what we use when we manage our projects. Get a better idea on how agile works by watching this video.

Agile Product Ownership in a Nutshell by Henrik Kniberg

Alan also shared a much funnier video: What would happen if Adolf Hitler attended a Scrum sprint review? (Be aware of some strong language used in the subtitles.)


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.



We received a question from one of our readers that asks, "How can the default font, font size, textbox height, defined?"

The answer is that we create a Template in Visual Studio or Report Builder that we can use in every report. That template will be opened by default when a user tries to create a New Layout.

In the Template that we create, we can set all the properties.

Follow ArcherPoint's blog – We will be posting a blog soon that details the steps for creating and modifying these templates.

Read ArcherPoint's Blog Follow us on Twitter Follow us on Facebook Follow us on LinkedIn Link to our RSS feed Join us on Google+ Watch us on YouTube