ArcherPoint Dynamics NAV Developer Digest - vol 91
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.
Saurav Dhyani shard a link about a new field in NAV 2016:
Kyle Hardin: I found this part of the article very interesting:
Note: We cannot add the field (Time Stamp) as a key in the table, but that does not prevent us from sorting on it. So SETCURRENTKEY will still add ORDER BY to the SQL query.
Jon Long: I think it started in 2015. SetCurrentKey is not necessary anymore.
Saurav Dhyani: That’s Right. From NAV 2015 onwards we don’t need keys even for calculation of Flow fields 🙂
Kyle Hardin shared this link on Windows and Linux:
Continuing our discussion from last week, Kyle share the following article:
Editor’s note: More and more, I find this move intriguing. Being a Unix developer and a Linux proponent myself, this represents a major shift in the way Microsoft has looked at Unix and Unix-like operating systems since the 1990’s. Quite frankly, it’s refreshing. There is a lot to be said for Microsoft development tools, APIs, and interfaces. But there are some advantages to Unix systems as well, as this article points out.
Dan Sass shared an article on the keys to a successful team (Google):
A study by Google reveals that “who is on a team matters less than how the team members interact, structure their work, and view their contributions.” This was a revelation to Google, and to most of us as well. The study also revealed the five key dynamics that are shared by successful teams:
Psychological safety: Can we take risks on this team without feeling insecure or embarrassed?
Dependability: Can we count on each other to do high quality work on time?
Structure & clarity: Are goals, roles, and execution plans on our team clear?
Meaning of work: Are we working on something that is personally important for each of us?
Impact of work: Do we fundamentally believe that the work we’re doing matters?
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.