Book Image

Microsoft Dynamics GP 2010 Cookbook

By : Mark Polino
Book Image

Microsoft Dynamics GP 2010 Cookbook

By: Mark Polino

Overview of this book

Microsoft Dynamics GP is an Enterprise Resource Planning system, essentially an accounting system on steroids, designed for mid-sized organizations. The implementation of Dynamics GP is usually considered to be complex, and people often realize there must be more efficient ways of working with the system. This book will show readers how to improve their use of Dynamics GP and get the most out of this tool quickly and effectively.This book picks up where implementation training leaves off. Whether you are new or experienced you will find useful recipes for improving the way you use and work with Dynamics GP. The clear recipe steps and screenshots make implementing these solutions easy for users of any level and will be sure to improve your efficiency with the Dynamics GP system.The book starts with recipes designed to enhance the usefulness of Microsoft Dynamics GP by personalizing the look and feel of the application. Most of the recipes are designed to give tips for a typical installation of Dynamics GP, including core financials and distribution modules. The book then moves through recipes that include automating Dynamics GP to allow users or administrators to focus on value adding tasks, harnessing the power of SmartLists to leverage both simplicity and power, connecting Dynamics GP to Microsoft Office 2007, exposing hidden features in Dynamics GP, and much more!By following the clear recipe steps and screenshots in this book, you will learn what is required to improve your efficiency with the Dynamics GP system
Table of Contents (17 chapters)
Microsoft Dynamics GP 2010 Cookbook
Credits
About the Author
Acknowledgement
About the Reviewers
Preface
Index

Improving performance by adjusting AutoComplete settings


Microsoft Dynamics GP provides AutoComplete functionality that remembers previous entries and displays them to users during subsequent data entry. Users can select the appropriate item without having to type the entire text. This is a great feature but the entries are stored per user and per field. This means that each time the system saves a vendor number that has been keyed it's saved as one entry for that user. By default, Dynamics GP is set up to hold ten thousand entries, per user, for each field.

As you can imagine, over a long period of time, and in organizations with heavy entry volume, the number of entries can build up slowing down AutoComplete performance significantly. Additionally, the number of choices presented to users can become unwieldy. For this recipe, we will look at a two-part solution to this problem. First we will set up a maintenance routine to clean out any entries not used over the last sixty days and then...