Microsoft Dynamics GP has advanced user-specific security settings to ensure that users cannot meander willy-nilly throughout the system and wreak havoc. If an organization properly implements the ERP system, there should be no problems.
Unfortunately, some organizations take shortcuts on setting up security roles, often to save time on implementation, and the results can be disastrous, often costing thousands of dollars to fix. Here are some specific, yet frightening, examples:
1. Delete company - Yes, a user with power user security settings can completely delete the company from the software. This is NOT good.
2. Remove history - Generally, you want history of your processes for accountability. Removing it is bad unless you are starting over.
3. Mass delete - Batch processes for deleting are good when intentional but very bad when done by mistake. Only an administrator should have access to this function.
4. Merging or changing customer or vendor IDs - For the purposes of staying organized, it is a bad idea to start fiddling with customer and vendor IDs unless you know what you are doing.
5. Closing the GL too soon - If a user is not restricted from closing the GL window, it can be closed prematurely and result in loss of data.
To find out 5 more scary ways users can mess up Dynamics GP, read the
CAL Business Solutions can help you implement Dynamics GP properly and avoid security and setup mistakes that can severely damage your company's ERP data. Or we can do an audit to confirm that your current setup is secure. Contact CAL Business Solutions 860-485-0910 x4 or [email protected]
By CAL Business Solutions, Connecticut Microsoft Dynamics GP partner,