Microsoft Dynamics GP Architectural Foundations Series - Built to Leverage

This is article 4 of 7 from the series Microsoft Dynamics GP Architectural Foundations Series - featuring Microsoft's Tim Brookins.

Tim's whitepaper was originally published in 1999 and it's reproduced here with his permission.






Built to Leverage

The previous two philosophies (“Built to Last” and “Built to Grow”) have ensured a feature-rich business management system that is ever growing. Each release builds upon the previous release, adding new functionality and technology. As functionality builds, the Dynamics product becomes a true asset to the business.

Our architecture needs to recognize the incredible value of this business asset and allow the business software engine to be used not only by Dynamics, but also
throughout the enterprise. As you will see, this is not a new idea. In fact, it’s been a goal of our architecture since the very beginning.

The diagram below shows the Dynamics’ business logic (the asset) in the large central box. The box on top labeled “Dynamics” represents the basic Dynamics user
interface. Of course, the standard Dynamics user interface leverages the Dynamics business logic to accomplish the required processing.

The whole “Built to Leverage” value is centered on expanding this usage of the Dynamics business logic to other non-Dynamics sources. The boxes labeled “Solution Developer” on the top are a great place to start. Since the first release of Dynamics, our toolset has allowed other applications to leverage the Dynamics business logic. For example, Solution Developer-produced vertical application could call the Dynamics posting routines. For the first release back in 1993, those Solution Developer products had to be written in our C++-based toolset (Dexterity). While this was a great start, we had a vision to extend this same ability to leverage the business logic of Dynamics to other non-Dexterity-based applications.

The box labeled “Continuum” on the left side is an example of how we’re delivering on this vision today. Our Continuum series of products allows an application written in any COM-compliant development environment to leverage the Dynamics’ business logic.

Our “Built to Leverage” architectural value has also allowed us to gain strategic advantage in the area of the Internet. For example, our support for electronic
commerce is enabled by allowing Microsoft Site Server to leverage Dynamics’business logic by exposing those business objects via COM. As we move into the future, additional components of the Dynamics business logic will be exposed to the Internet as Microsoft Transaction Server-based COM objects.




In the next article Tim reviews "Built to Fit".

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more