The Five Microsoft Dynamics GP “Worst Practices”

Articles often highlight best practices, that is, the consensus right way to do things. I've decided to take a look at some common worst practices. These are practices that organizations should discontinue with Microsoft Dynamics GP. Here are five of the worst:

1) Ignore Backups

Companies know that they should backup their Dynamics GP data, and may even think that it's being backed, but unless they've done a test restore, all they have is a hope and a prayer. Users need to stop guessing and ensure that the GP database is being backed up (not just replicated via a RAID system or stored on a SAN). Users should check that customized forms and reports, along with integration manager databases and the FRx SYSDATA file, are all being backed up. Some configurations may even have more items to back up.

2) Load up the Chart of Accounts

Some users are like pack rats--they like to store everything in the chart of accounts. They have a segment for customers, a segment for projects, a segment for fixed assets, and often a blank segment for certain one-off transactions. Stop! Slim down the chart of accounts and let Dynamics GP's sub-ledger connections provide the needed reporting, without bloating the chart of accounts.

3) Customize the Interface Instead of Changing the Process

Customizing the application is fine, but customizing the interface instead of changing the company's process is a recipe for scope creep, increased costs and upgrade problems. Customizations should add value, not simply reproduce what a company already does. Too often, the old process is in place because of limitations from a previous system. Companies that start working with the default interface are ...