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.

They spot checked the GL accounts on the error log + the accounts not on the error log.  Everything is still inactive, except the ones on the error log, because they were never inactive as they had a current balance.

OK.  Well, against all logic, I suggested running it again but choosing TRUE instead of FALSE.  The field is Inactive so TRUE should ‘inactivate’ it, but stranger things have happened, and it’s worth trying.  I thought there is a chance that it is working backwards for some reason.

Same issue.  Huh.

Well… let’s get rid of the Use Input and put it back to Use Constant and set it to False.  Run the integration, it works like a charm.

So, in this bizarro world, Use Input apparently ignores whatever the user selects in the drop down list and runs the integration as “Inactive = True”.  Using a constant works.

Go figure!  Just when you think you’ve seen everything, something new and strange pops up!

(for reference, the client is using GP 2010, and Integration Manager 11).

(originally posted on www.kuntzconsulting.ca, and migrated to this site in October 2017)

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

  1. Reply
    Chris - June 27, 2013

    How did you inactivate the accounts once they had a balance?  We had several departments move and I wanted to inactivate old accounts that had old location number.  Same error “account has balance”.  I used constant as well.  Problem is when you inactivate manually….a prompt pops up verifying you want to inactivate since account has balance.  And the integration can not handle this pop up prompt.

    1. Reply
      Jen Kuntz - June 28, 2013

      Hi Chris,

      Thanks for the comment/question.  Long story short, you’re correct, Integration Manager cannot handle the “validation” side of the prompt where inactivating an account manually, at least you have the choice to manually make that decision.

      Re-reading my own article I realized it wasn’t very clearly described. In my client’s case the issue was that Integration Manager kept trying to inactivate accounts no matter what “use input” value you used; they were trying to activate a bunch, and included all accounts they were working with, some of which were already active anyway.  It seemed like a bug.

      Suggestion: if it’s a certain segment value, try Mass Modify (Cards – Financial). One of the “mass modify” options is Inactivate. I only have GP2010 in front of me (not older versions) but if you choose that, it gives you the option to mass inactivate only zero balance accounts or all accounts and allows you to do it en masse like you might be trying to do with IM.  That could work for you instead?

      Jen

      1. Chris Bishop - June 28, 2013

        Thanks for trying to address my problem.  My first inclination was to use mass modify, but I couldn’t isolate those departments.  The location is still in use and would inactivate all accounts.  I have no experience in scripting and was hoping that might offer solution.  We have moved forward with just manually inacivating.  I would have preferred better solution as I’m sure we will encounter again.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top