Friday, May 16, 2008

Importing data to GP

I've seen a couple of post requiring data to be imported into GP but needs to be QA'ed. Example, let's say you have an e-Commerce system where orders get created and are manually entered in GP as Sales Orders. While entering in GP, the user make changes to amounts, quantities, prices, costs,etc.

Over the years, Microsoft Dynamics had been creating tools to make integration easier to manage. You can create interfaces using GP Web Services and this can reside outside GP where you can QA data before the actual import happens. The advantage? You're not using any GP license.

Another tool you can use - eConnect. A lot of GP vendors have created eConnect templates for ease-of-use and faster ROI.

You can also look at SQL Server Integration Services. This improved version of DTS is a true ETL solution for enterprises.

My 2 cents, spend more time choosing the right tool as each can have their pros and cons. Also consider creating a Staging database when you're not sure if data is reliable enough to be imported to GP.


Anonymous said...

i did a little research after you told me about your "thing", and if you want a way to make more money using your your blog you can enter this site: link. bye.

Anonymous said...

I would suggest using SQL Server Integration Services in combination with the Dynamics GP SSIS Toolkit rather than going through the hassel of creating your own windows service that interfaces with eConnect.

With SSIS you can customize every aspect of the integration with .NET code if you wanted to but most of the out of the box adapters will get you what you need such as event logging, email functionality, automated webservice and FTP interaction etc.

The toolkit integrates all the business objects that are supported by eConnect and is 1/5 the cost of integration manager or Scribe.

The Dynamics GP SSIS Toolkit can be purchased here:

Anonymous said...

hi mate, this is the canadin pharmacy you asked me about: the link