ArcherPoint Dynamics NAV Developer Digest - vol 43
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 on the Enhanced Security Model in Dynamics NAV 2009:
I have a client running Enhanced Security on Dynamics NAV 2009R2 Classic. Is there a downside to turning this feature off? And are there any unintended side effects of doing so?
There is a possible issue with the standard model. Note the following article:
There are blogs out there that talk about the futility of this legacy mistake. It no longer exists in 2013 and beyond.
And here is some background conversations on this subject. According to this post, survey says, 0% of developers say Yes to Enhanced.
Question: In Project Management, what’s the difference between Forecasting and Scheduling?
In general, forecasting focuses on long term role demand, while scheduling focuses on short term resource demand.
Forecasting derives the demand for roles within a time bucket based upon sales forecast, booked projects and work effort trends. For example: a forecast will tell you the total number of consultants needed in the month of August to satisfy the total estimated demand.
Scheduling derives the specific resource assignment based upon the booked demand for a role. For example: a schedule will show a resource by name to satisfy a specific project role during the months of July and August.
Dan Sass offers this practical definition of reputation:
Reputation is what people expect us to do next. It’s their expectation of the quality and character of the next thing we produce or say or do.
We control our actions (even when it feels like we don’t) and our actions over time (especially when we think no one is looking) earn our reputation.
– Seth Godin