A Dynamics GP Showdown: Customized Solution vs. Third Party App

A Microsoft Dynamics GP implementation has many variables that go into making the project a success. The right modules need to be selected, a plan with a solid methodology needs to be in place, and the key stakeholders must be involved in every step of the decision making process.

In many instances, native features of Dynamics GP solution fall short in terms of scalability. Many of these shortcomings, if accepted as they are, could create solution adoption risks that would have been avoidable if other viable options were explored. One of the strengths of the Dynamics GP architecture is its ability to integrate seamlessly with other applications, opening up a host of opportunities to incorporate function-specific tailoring to fit with any business model.

Qualifying a custom solution

When an organization decides to look beyond a standard feature, they have a few options: have a custom application built, modify the source code of GP itself using Dexterity, or employ the use of a Microsoft-approved third party add-on.  When looking for a solution, the best questions to ask are whether it will:

• Be easy to make compatible with future versions of Dynamics GP?
• Prevent an upgrade to GP because it has modified program source code that will not allow the upgrade to process as designed?
• Be so complex that it holds you indebted to an individual that created the application?
• Follow all of the data validation rules that are inherent in Dynamics GP but not necessarily be adhered to with a program pushing data in through SQL?
• Easily adapt for new technology that is developed?
• Be intuitive for the end-users?

Compatibility is key. For example, does ...