subject: Dynamics Gp Customization In Dexterity Faq [print this page] Corporate ERP system is often something that got to interoperate with external databases and applications. In order to make the job done you have to create new tables and open them through user interface. Historically Great Plains Software introduced its Dynamics back in earlier 1990th as application coded in Dexterity IDE (Integrated Development Environment) where programming language is semi-proprietary with the name Sanscript. Dex is in its turn the shell developed in C. If you remember the time in earlier 90th where ERP vendors have to balance on various operating systems and database platforms such as Microsoft Windows versus Mac OS as well as SQL Server, Sybase, Oracle, Btrieve and Ctree to name a few. In this publication we do not pretend to be technical as it is rather for internal project manager. We will mention what is important and how to retain control over your custom module:
1.Sanscript and GP architecture. It might be not too complex language as it resembles Visual Basic. However Dex expertise comes together with table structure and business logic experience. It is not realistic to expect internal programmer to get the tool over the weekend or even over the month. We would rather recommend to contract technical consultants to do the job. Local consulting firm might be not really position to help you with Dexterity as it typically has to concentrate on functional consulting and new software licenses sale. Be ready to appeal to nationwide ISV partners running software development factory departments
2.Packaging and distribution. Custom module is distributed in the form of so-called chunk file (with extension CNK). Developer takes clean copy of Dynamics.dic and write scripts as well as creates new tables and forms there (plus modifies existing forms but this method is not neutral to future version upgrades). When chunk file is created all the scripts are stripped out and this is why we recommend you to pay attention to source code ownership (read next paragraph). Distribution is simple all you need to do is to copy the file to user workstation folder and at the next login code will be integrated and registered in Dynamics.set file
3.Source Code. Customer and consulting firm may have conflicting interests. Consultant is not interested to hand over to youre the code itself and retain its ownership for the future upgrades and further developing. Of course many managers believe in long term partnership with technology organization. But the real life shows the patterns where partners are keeping relations for several years and then walk away from each other. Sanscript codes are stored in Dynamics.dic (or Extract.dic) dictionary used in development project. Be sure that you have these files in your disposition and store them in your archive. If you do not have it then future version update might be complicated and if code revision is required (likely) then programming should be redone from scratches
4.Alternative tools. With the introduction of Microsoft Dynamics ERP brand we see such new instruments as eConnect, Visual Studio Tools, Web Services just to open the list. There is still dependence on Dexterity as such objects as new tables got to be created there in order to be accessible by VST for example. When somebody is too optimistic about new instruments we recommend you to check references and see how long the specialist is in consulting business
5.For additional information, please feel free to call us 1-866-528-0577 or 1-630-961-5918 (this number works for international customers) or email us help@albaspectrum.com We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences). Local service is available in Western Michigan, Chicagoland, Southern California (LA, Orange County and San Diego), Houston area of the state of Texas
