Protect Your Investment: Five Things You Must Document in a Microsoft Dynamics GP Solution
Quite often in the last few years I have received a call or email that sounds something like this: "I have recently started working for a company that is using Dynamics GP and have been tasked with helping users address their various questions on it. At the same time, management would like to make sure we are utilizing Dynamics GP to its fullest potential and would like to add/streamline functionality. However, my first task is to get a handle on all the various components we have, as nothing is currently documented."
This is, of course, the cleaned up version. The real conversations usually touch on how difficult it is to find any information, turnover in the IT and accounting departments, and how no one in the company remembers anything about customizations, modifications or any reasoning behind them.
I believe there is an important lesson in this: no matter how fabulous your GP partner is, no matter how ‘vanilla' your Dynamics GP implementation, you still have to be responsible for your own documentation and need to make sure there is an internal resource in charge of gathering and maintaining all of it.
Whether you are just starting to implement Dynamics GP or have been using it for 15 years, here are five things to make sure you have a well documented system:
-
Your
Microsoft Dynamics GP licensing. Don't
forget to include FRx, Management
Reporter, and any 3rd party (aka ISV) products. This can be important when planning changes -
for example your licensing might be limited to a certain number of users or
already include modules you want to use in the future, making the decision to
add ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us hereor login