cancel
Showing results for 
Search instead for 
Did you mean: 
Workflow Hero

Dynamic GP Integration

Jump to solution

Hello wonderful community...

I'll soon be doing a Nintex workflow to integrate and update information with Microsoft dynamics great plains (GP) (not CRM). I heard it is the same platform but just some additional functionality are in CRM. 

Does anyone know what type of connector it would use? SOAP/RESTful/oData..etc? In the web service action I can only see SOAP? or do we need a custom connector..etc.

I can see one question asked in the community before about GP but got no answer. 

https://community.nintex.com/message/50825-re-dynamics-gp-2013-r2-and-nintex-workflow?commentID=5082... 

I don't have much info and this is pretty new. I'm in the process of gathering information from different resources. The more details any can provide, the better.. Thanks all.

Labels: (1)
Reply
4 Replies
Workflow Hero

Re: Dynamic GP Integration

Jump to solution

Tagging some folks who might be able to help ye out here: 

Casting a wide net since this is pretty specific stuff.

Reply
Workflow Hero

Re: Dynamic GP Integration

Jump to solution

Christine Mikhaiel‌ - 

I am not vary familiar with Microsoft Dynamics GP, but if there is a service layer, you can definitely leverage that to perform your updates.

I would check out Web Services for Microsoft Dynamics GP  as a starting point and go from there.

What version(s) are you using for Nintex? SharePoint?

Reply
Workflow Hero

Re: Dynamic GP Integration

Jump to solution

Thanks

Thanks ‌. I'll check the link out. 

It is SharePoint/Nintex 2010 and very soon this year (after we implement this one), we will be moving everything over to O365.

Reply
Workflow Hero

Re: Dynamic GP Integration

Jump to solution

We ended up dealing with it as any other application with SQL server as its database. I used sql action on the form to pull a list of active vendors from GP. And then at a certain stage we are creating transactions/batches.. all that fun stuff through stored procedures and executing those stored procedures on the query sql action - one stored procedure at a time. 

Also that was our only option since the web services were not installed. 

In the future, we might look at getting "Scribe" as an integration API, but the sql and the stored procedures did the trick for now, plus it is more manageable for what we are trying to do which wasn't really much. 

Reply