ArcherPoint Dynamics NAV Developer Digest - vol 30
The ArcherPoint technical staff—made up of developers, project managers, and consultants – is constantly communicating internally, with the goal of sharing helpful information with one another.
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.
Question about the pros and cons of using Deposits vs Cash Receipt Journal:
Question: I naturally gravitate to the Cash Receipt Journal for cash receipt processing. What are the pros/cons of using Deposits vs CR Journal?
Answer from Crystal Tollison: The Cash Receipts Journal has several issues a client may have to figure a work-around for based on the technical structure of the journal itself which is just a standard General Ledger Journal like the Sales or Purchase Journal. The Deposits function was created to eliminate some of those issues and is structurally different with a header and lines design instead of a journal. The biggest issue that it resolves is the ability to apply a short pay the way you want when there are multiple invoices/credit memos applied to the payment. The CRJ makes the application based on some logic that I have yet been able to decipher and the user has no control whatsoever. Let me know if you want a demo of what I’m talking about and we can do a screen share.
Bill Warnke shares his favorite NAV development tools:
Hi everyone. I’d like to share two of my favorite NAV specific tools. I’d love to hear about any utility type programs that anyone else might use.
Statical Prism – Blazing fast C/AL code and relationship analysis. I hope they keep up with the development because it’s a very handy tool.
Finn’s FobView – I mainly use it to automatically mark objects in the object designer from a FOB or TXT and then set the Marked Only filter.
The following articles offer some useful NAV resources to developers:
Cached Web Service Calls
In a service-oriented deployment, web services are used to extend NAV’s functionality and reach. Depending on how volatile this data is and the corresponding usage scheme, it is expected to be up-to-date within a pre-defined period of time (e.g. once a day).
.NET Exception Handling in C/AL
When there is a need to use .NET classes within C/AL, one of the main challenges is to handle the exceptions the methods of these .NET classes may throw. Eventually, if not handled, they will basically bubble up as runtime errors, halting the current operation a user is doing without having a chance to properly display errors in a user-friendly format.
RDLC? That’s easy. Everyone can do it…
An article by Mark Brummel about how even non-developers can create RDLC reports.
Free Visual Studio designer for NAV 2015 and NAV 2013 R2
This article by Claus Lundstrom talks about advantages of using Visual Studio over Report Builder and offers tips on installing it.