Using eConnect from Dynamics GP Dexterity

I have recently been switching all of my Dexterity code to use eConnect procedures to add data to Dynamics GP.  I find this combination greatly simplifies both my Dex code and efforts to develop and maintain the code.

As far as I know if you use Dexterity you have three choices if you want to get data into Dynamics GP tables:

1. Use the process described in the SDK.  This seems very complicated to me whereby you invoke forms in an object manner.  I'm opting to avoid this until I can find something that points me to how this can be done in a simple and straightforward fashion.

2. Code directly to GP tables from Dexterity.  This is borderline foolish.  If you develop this way when you move to a new GP release you must adapt your code to any table or business rule changes that apply to those tables you interact with.  Not only that you must know and understand the rules of every single field in the table before you can load data.  I started doing this but knew all along I would not be able to sustain this code.  That's why I chose the next option.

3. Use eConnect calls from Dexterity.  This has turned out to be a very simple way to get data into Dynamics GP safely and with minimal effort for GP upgrades and updates.  I have been using eConnect for years by way of Scribe Insight and it's extremely robust, reliable and fast.  Using eConnect makes upgrades painless.

I don't know what other Dexterity developers are using to get data into GP but I am offering to publish a How-To guide if there is interest.  Please let me know in the comments if you would like me to publish and I'll proceed.