ArcherPoint Dynamics NAV Developer Digest – vol 60
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 shared these Dynamics NAV reporting tips:
To view the data set for a report, you have preview the report then click Help > About This Report. But that just enables the feature, and you have do the whole thing again to get it to actually work.
Before previewing the report you can also click Help > About This Page on the Request Page. Then when you preview the report the data set will be enabled. This is especially useful for those reports that you know will take a long time to execute.
If you need to start over with a layout you can set the ProcessingOnly property to Yes, then back to No.
Question on an error message when posting a General Journal Entry:
Question: Has anyone seen this error message in NAV 2013 when you post a General Journal Entry:
"You do not have the following permission on TableData Cost Accounting Setup: Read"
The permission error is caused by a record in the Cost Accounting Setup table (1108). After deleting the record it still will not allow me to post.
Faithie Robertson: I ran into this during an upgrade at a client site. What happens is that the setup table receives a blank record when they open some page in the new area (sorry - I don't remember which). The problem is that since it's a blank record, you can't really “see” that it's there, but it doesn't pass a code statement that checks to see if the table "ISEMPTY"...and then you get the error. Since the client had multiple companies and each company could have a record, the solution was to create a report that cycled through each company and deleted the record. I hope that helps. :)
Dan Sass shared an article on avoiding email embarrassment:
Ever respond to an email and, seconds after hitting send, wish you could somehow take it back? If you answered “no” to that question I would wager you have never worked in an office before or you are still on in your first week at your first job.
There are a number of reasons why this might happen, but in all cases it usually ends up that you have to make an explanation to someone about what you did and wish you didn’t.
Dan Sass shared an article that talks about how to avoid these embarrassing and potentially career altering situations. Read the full article:
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.