You can develop applications that seamlessly integrate with Microsoft Dynamics GP, so that the user will not be able to tell when your code is running versus the original Dynamics GP code. Creating such integrating applications first requires that you have an intimate knowledge of Dynamics GP's architecture. By architecture, we mean the design that allows the product to evolve with technological advancements and embrace the increasing demands for performance and capacity. This lasting design is a framework of interdependent components that weave together to create the application we know today. Understanding the components of Dynamics GP and how they work together will prepare you to design a solution that will evolve alongside Dynamics GP as it meets the demands of this ever-changing market.
This chapter is a 10,000 foot view of Dynamics GP, how it was built, why it was built that way, and how this affects your application. Upon completion of this chapter, you will understand the components that make up Dynamics GP and how your application fits into that architecture. This chapter will provide an overview of the following topics:
The native user interface
Dexterity overview
Components of the Dynamics GP application
SQL table and procedure names
What you see – the user interface (UI)