Today at the MS Dynamics World Decisions Fall 2010 virtual conference, I gave a presentation on the Dynamics GP Developer's Toolkit. After the presentation, I had about 30 minutes to answer questions from attendees.
One of the attendees asked if I knew of any good diagram or documentation, other than the SDK, of the Dynamics GP database tables. The attendee wanted to know how to learn the Dynamics GP database tables so that he could start developing customizations and integrations.
My recommendation was to first understand the history and design behind the GP table naming convention. Once he had that knowledge, he could then more effectively use something like the Resource Descriptions windows within GP to locate specific tables.
I referred him to David Musgrave's excellent discussion on the topic:
http://blogs.msdn.com/b/developingfordynamicsgp/archive/2009/05/29/understanding-how-microsoft-dynamics-gp-works-with-microsoft-sql-server-continued.aspx
David's discussion was much broader in scope than just the table names, but in the post above, he does an excellent job of describing the history and design of the table and field naming conventions. With this information, a developer can have a very good understanding of how most of the company database is structured and how to find specific tables.
Steve Endow is a Dynamics GP Certified Trainer and Dynamics GP Certified Professional. He is also the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.
http://www.precipioservices.com
1 comment:
Don't forget the Support Debugging Tool's Resource Information and Resource Explorer windows.
http://blogs.msdn.com/developingfordynamicsgp/pages/support-debugging-tool.aspx
Or the script to export all the information to a text file:
http://blogs.msdn.com/b/developingfordynamicsgp/archive/2010/07/07/getting-table-and-field-data-out-of-dexterity-dictionaries.aspx
David
http://blogs.msdn.com/DevelopingForDynamicsGP/
Post a Comment