Custom Development for Microsoft Dynamics GP 10.0 Great Plains

Custom Development for Microsoft Dynamics GP 10.0 Great Plains

Former Great Plains Software Dynamics, later one Microsoft Great Plains, and currently Microsoft Dynamics GP 10.0 is the successor of Great Plains Software Dynamics, IDE, and programming language. It is pretty typical as GP development tools moved to the new database platform: Microsoft SQL Server, or the newer name: SQL Server Edge. There are several options on the market, however, if you look at the e-commerce platform, you will see that such popular among developers as Amazon, eBay to name large online stores, also blink and so on. For e-commerce programmers, the most challenging is eCommerce integration, where you should be able to process credit cards purchases into GP on the Sales Order Processing, SOP, GL, IV, Payroll or Payroll Payroll Payroll modules, shipping to SOP or IV and you are currently doing Sales Order Processing custom logic, where you should be able to invoice your customers and mark them as completed on your Sales Order Processing module. This seems to be easy however technology has advanced and ERP vendors are providing you e-commerce integration module: Microsoft Dynamics GP eConnect. Also interesting for developers is eConnect – SDK for Microsoft Dynamics GP. Let’s move to the topic:

1. eConnect overview. When you need work with Microsoft Dynamics GP “fat client” – which is Sales Order Processing, you use eConnect, which is architected as so-called typed pool approach. This means that each company can work with its own GP workstation and this “fat” client will in turn work with collection of workstations from another company. What is the limitation of this approach – you can not do posting from one workstation to another company ( reviewer should be aware that this is not the only limitation, see the next part). Currently Microsoft recommended is doing data translation – from Text (txt) format to GP varieties of. When you transfer your text file and open GP workstation, old Text files will be converted and updated – the conversion should be finalized with Text to GP converters, available from third party. Old good functionality likely will be hidden and repurposed, for example you can not post Lead Mail from Great Plains, but you can post custom text messages from custom Lotus Notes.
2. Text to GP converters. You will need custom text converter, available fromwww.Mechat depositories.comISStock: Registered in the e-mail purchasing department, so you should not hesitate to contact them. All you need to do is provide your deposit Documentation, preferably with Invoice header. See your Supply Chain Management plan for Invoice header, lines, source: investor_name, amount: amount_to_deposit
3. eConnect overview. When you implement eConnect – you will receive objects, created with eConnect andTransact SQL scripting. You can manipulate these objects and create transactions or batches and all the rest of the posting logic is exposed to you. You can create or delete batches and all the rest of posting logic is exposed to you. You can schedule your posting transactions. All the posting logic is exposed to you. You can, for example, create Sales Order and initiate posting on the server automatically.
4. Emailing scenarios. It is common to see the need to build custom logic to be able to work with Microsoft Outlook. Getting Microsoft Dynamics GP workstation active andBobrows server workstation active – incoming email is sent directly from GP as batch, and incoming email is received from outlook. Each batch also could be bound to an activity and the batch activity is posted automatically when the batch is received.

Happy customizing!