Prior to version 7.0 Great Plains had plans on expanding GP functionality and so was changing tables structure ? forcing Dexterity customization to be analyzed and partially rewritten with each upgrade. Not any more ? GP structure stays the same ? Microsoft is doing new modules acquisition and unifying it's graphical interface to move all it's ERP packages: Great Plains, Solomon, Navision and Axapta to web-based Microsoft Business Portal.
Still pain. Dexterity has possibility to customize existing Great Plains screens, so called Alternative Great Plains forms. This was upgrade problem in the past and it stays now ? there is no way to do it in house (until you are willing to pay for full-time internal developer ? who is usually in the learning curve). You got to bring in consultant.
Recommended approach. You should have the strategy to migrate Dexterity customization to SQL, Crystal Reports, custom web publishing ? Visual Studio.net and slowly abandon Dexterity customization
#SQL Stored procedures - performance improvement. Consider replacing dexterity data manipulation with SQL stored procedures. Dexterity is cursor-driven language and it is not efficient when processing huge datasets.
# Do direct web publishing off your GP database. Use Visual Studio ? it is easy to find specialists and have them in staff. We are in the World when web publishing is very easy.
This is a very informative article.I was looking for these things and here I found it. Registered Nurse auto insurance discount
ReplyDelete