Monday, May 23, 2011

Microsoft Dynamics GP "12" Named System Database Architecture

I received a lot of feedback from the community as a whole on the 3-part series of articles on Microsoft Dynamics GP "12" Web Client Architecture and I was pleased to know that many of you are embracing the fact that there will be a Web client version of the product and are asking numerous questions about readiness.

While these articles addressed the client portion of the solution, I really did not mention anything about changes in the database architecture and how these will impact the future deployment options. So, I have released a new architecture article on Microsoft Dynamics Community, this time addressing Microsoft Dynamics GP "12" Named System Database Architecture.

In this article I look at the named system database capabilities to be released in GP "12". This is, the ability to set any name to the traditional, hardcoded DYNAMICS database. Hope you enjoy the article and if you have any comments or questions please feel free to post back.

For convenience sake, I will be adding a new link to the architecture series.

Until next post!

Mariano Gomez, MVP
IntellPartners, LLC


06/06/2011 - Changed article title to fit instructions provided by Microsoft Escalation team and current developments out of Fargo.

1 comment:

Anonymous said...

Will you be talking about 3rd party integration that is not Dex related? It is possible to popup or embed a html page from a Dex form? We currently have a window in a dll that we popup from our dex module. I'm hoping we can convert the window to a web page and display that.