I am working on a Purchase Order integration with GP 2013 which has been working fine for awhile, in testing. I am using SmartConnect to integrate incoming POs
Just recently, even though there are no changes to the source data, or the SmartConnect maps, eConnect is suddenly complaining of an Invalid Buyer ID
I am not sending Buyer ID in the map as it is not a requirement. Something about GP changed to cause eConnect to start complaining about invalid Buyer ID. The people in charge of the GP side have been fiddling with GP but are not being helpful in understanding what has changed.
What changes in GP could have possibly caused this to happen? Buyer ID is never required and is not sent in my XML so I am completely stumped.
Any help would be most appreciated. Thank you
*This post is locked for comments
I have the same question (0)