ArcherPoint Dynamics NAV Developer Digest - vol 64
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.
Matt Traxinger on NAV Reporting:
If you need to add fields to a SetData command, don’t add them in the middle. You’ll need to add them to the end of the string so that you don’t make all of the other GetData text boxes reference the wrong field.
Kyle Hardin on .NET SQL calls and NAV errors:
Important Safety Tip: If you are using .NET calls to insert or modify data in another SQL database, remember that a NAV error and its rollback will do nothing to your SQL call. If the sequence of events is this:
DotNet SQL Insert
Then the NAV error gets rolled back, but the SQL insert stays. It happened in its own transaction, and that transaction completed successfully.
I’m only posting this because my best friend’s sister’s boyfriend’s brother’s girlfriend heard from this guy who knows this kid that said that someone might have accidentally had this problem…hypothetically, of course.
Dan Sass shared an article on handling a severe stress episode:
EDITOR’S NOTE: We’ve all had stressful events in our lives. Some of us have even experienced stress meltdowns that severely impaired our ability to successfully complete the task at hand. This article shows us that the stress episode is natural, yet does not have to be catastrophic. Recognizing what is happening is the key to begin to deal with a stress episode. Please be aware, though, that the word “Simple” in the title may be a little misleading – here it means “uncomplicated”, not “easy”.
Read the entire article: A Simple Yet Powerful Way to Handle a Stress Episode
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.