eConnect error, but not the real error!

One of my customers is doing some Sales Order Processing integrations with GP2010… and for the most part, when we run into eConnect errors, it pretty much tells you what the issue is, and you fix it and move on.

We ran into one the other day and this error wasn’t even the real error, so it wasn’t until I looked at the XML they were trying to pass did I see what the real issue is.

eConnect error “configured identity is incorrect”

A client recently had an issue with their nightly eConnect integrations, getting an error about the username and password.

This integration had been live for nearly 2 years, running every night, and running without issue – or at least without this kind of issue. In other words, fairly stable.  They also never touch the service accounts, so the thought that the password might have been changed was nearly impossible.

Bizarro world: Integration Mgr “use input” doesn’t work

This is a short post… a bizarre issue that I can’t find an answer to.

A client has a bunch of inactive GL accounts and for a project, wants to re-active them to do some re-allocations and then inactive them again.  Simple right?

I set up a simple Integration Manager integration for them, and set the “Inactive” field to “Use Input”.  In other words, let the user decide if they are inactivating or re-activating the accounts.  Better than changing the integration, right?

Seemed like a good idea at the time.  So we set the field to Use Input and then they ran it, it gives them a drop down list, and they chose False, as in “re-activate”.  They run the integration and start getting a bunch of errors “This account has a current balance”.  Hmmm.  That should not matter if you are “activating” so I didn’t understand the message.