63
Hello Team,
I am searching for a partner who will be able to help us with technical questions according to the integration with Microsoft GP.
If there is anyone on the forum who can, on a cooperation basis, help with integration issues with Microsoft GP?
Hi Andrew,
Why try to re-invent the wheel when there are affordable 3rd-party solutions out there that will save you the headaches of developing your own connector..?
www.kingswaysoft.com/.../ssis-integration-toolkit-for-microsoft-dynamics-gp
or
smartconnect.eonesolutions.com/
There are other options out there, but try to stick with true-and-tested solutions..
Hi Andrew,
Sorry, I cannot provide any assistance with GP Web Services. I never implemented for a customer and recommend that GP customers do not use it. I do not provide any support for GP Web Services.
There is zero documentation on the XML payload or SOAP structure or the authentication mechanism for GP Web Services, and there is zero support for attempting to integrate with GP Web Services outside of .NET.
If you insist on using it, I can only recommend that you use the supported integration method with Visual Studio and .NET.
Steve
Hello Steve,
Maybe you could help me with this question from my DEV Team.
They have GP WebServices installed and running. Also, they are trying to invoke sample service (GetCustomersList action), but getting this error:
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="schemas.xmlsoap.org/.../s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="en-US">The message could not be processed. This is most likely because the action 'schemas.microsoft.com/.../GetCustomerList' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
Based on my research it means that WSS headers required by the service are not provided, or are incorrect.
Native endpoint is set to use wsHttpBinding with the following definition (default from WSBinding config file):
<security mode="Message">
<message clientCredentialType="Windows"/>
</security>
They tried to use these headers without any luck:
<soap:Header>
<wsse:Security mustUnderstand="1" xmlns:wsse="docs.oasis-open.org/.../oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-5700630" xmlns:wsu="docs.oasis-open.org/.../oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>someUser</wsse:Username>
<wsse:UserTokenID>somePassword</wsse:UserTokenID>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
Question:
What should be the SOAP header structure in order to meet this requirement and properly authenticate with the service? I have a Windows user account with proper permissions to access Web Services.
Could you share an XML example?
Totally agree with Steve Endow, I worked with C#+WCF using eConnect.
Check these two links, may be you will find something or get better idea to redesign.
This won't be the answer you want to hear, but this is my personal opinion based on my experience.
1. Do NOT use GP Web Services. Period. You are seeing the issues trying to integrate them with non-.NET tools, and very few people use them or can support them, so I do not recommend using them at all. Years ago, I had the exact same issue you are encountering with GP Web Service authentication with Jitterbit, and I was unable to solve the problem. GP Web Services works great with .NET, but it is a nightmare to use with non-.NET tools. I refuse to support GP Web Services due to the issues that customers have encountered.
2. Redesign your GP integration to be asynchronous. Do not make direct web service calls to GP, but instead use an async file-based or database-based integration. This will allow you to use conventional GP integration tools (eConnect, SmartConnect, etc.) on the GP side, which will be much more supportable long term for the GP customer.
3. If you believe that you absolutely must have a synchronous web service integration, my recommendation is to develop your own custom web service that calls SQL queries to get data from GP, and/or uses eConnect to import data into GP. I have used ASP.NET and ASP.NET Core, and those solutions have worked very well. You can then expose those custom web service endpoints to your integration, using whatever authentication will work for you. But note that the eConnect .NET assemblies use .NET Framework, so they cannot be referenced with newer versions of .NET Core (I think v2.1 was the last version that supported Framework references).
If you insist on using Java to try and call GP Web Services and are unwilling to redesign your integration, I suspect you will have a very difficult time finding someone who can assist you, as it is not a supported scenario for GP Web Services.
David,
Could you recommend people who can help us?
Could you provide your email adress?
Hi Andrew,
I am an freelancer and wants to know more about your requirements. Please feel free to visit my blog and contact me on my email address.
DD- blog | contact me
Hi Andrew
I don't have any experience using the SOAP based web services, so I cannot assist.
Let's see what the community says.
David
#1
André Arnaud de Cal...
294,137
Super User 2025 Season 1
#2
Martin Dráb
232,879
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
