ArcherPoint Microsoft Dynamics NAV Developer Digest - vol 4
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.
Faithie Robertson on using the Quick Filter in Dynamics NAV 2013 / 2013 R2
Here’s a great article about the redesigned Quick Filter in Microsoft Dynamics NAV2013/2013R2 and how Update Rollup 13 for Dynamics NAV 2013 can correct the use of the filter using wildcards.
Using the Quick Filter in Microsoft Dynamics NAV
Michael Heydasch added:
I think the new approach is more intuitive. Previously when I searched, I always entered @*characters* which translated to “find any result that contains ‘characters’, and I don’t care about uppercase/lowercase”. Now, I can just type “characters” and it translates exactly what I want. If there’s a filter character like *, then pay attention to what I’m typing.
Alan Campbell on Velocity using agile:
Velocity: A key tenet of agile estimating and planning is that we estimate size but derive duration. Fortunately, as a team begins making progress through the user stories of a project, their velocity becomes apparent over the first few iterations. The beauty of a points based approach to estimating is that planning errors are self-correcting because of the application of velocity.
Suppose a team estimates a project to include 200 points of work. They initially believe they will be able to complete twenty five points per sprint, which means they will finish in eight sprints. However, once the project begins, their observed velocity is only twenty. Without re-estimating any work they will have correctly identified that the project will take ten sprints, rather than eight.
The beauty of this process is that estimating in story points completely separates the estimation of effort from the estimation of duration. Of course, effort and schedule are related, but separating them allows each to be estimated independently. During the project, you are no longer estimating the duration of a project; you are computing it or deriving it based upon empirical evidence. The distinction is subtle but important.
Jon Long offers these Tips and Tricks:
The System Indicator on the Company Informantion Card can be used to display System Info. on the top ribbon in RTC clients in 2009R2 and beyond. The System Indicator(Accent) can be used to control the background of the control. This can be pretty useful when you have an environment that has multiple companies/db’s (in Test environments, for instance).
You can open a FOB in Notepad to see the object lis with each objects metadata, i.e., Number, Name, Version List, and Date/Time stamp.
Ever need to delete a file in NAV, after a DataPort Import, for instance?
ERASE(FilePathAndName);
Pretty slick.