After my last post debacle (if you missed it, you missed it!), I’ll stick to blogging about things I know best!
This is a strange one, one of those things that makes you go “hmmmmmm”. I never understand how this happens, if it’s been here for years or just never been noticed?
Continue reading “Cdn Payroll – Things that make you go hmmmm”
One of my customers is doing some Sales Order Processing integrations with GP 2010… 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.
Continue reading “eConnect error, but not the real error!”
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.
Continue reading “eConnect error “configured identity is incorrect””
A couple of years ago around this time of year, I got a call from a client of mine with a strange error in Canadian Payroll. At the time, I ran into other significant issues in trying to help with said error, and at the time, I blogged/ranted about it here.
Fast forward to last month, when I received an email from another customer who was asking me “did you ever find out what the issue was with that error? We are having the same problem now!”. We exchanged emails and I researched what notes I had taken at the time, and in the end, she confirmed for me that what worked for my client also worked for her.
So, this post is just an update on the issue and at least one resolution, in case it helps someone else out there. Some of this is a repeat of the rant blog, without the rant!
Continue reading “Update on Account Number error in Canadian Payroll”
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.
Continue reading “Bizarro world: Integration Mgr “use input” doesn’t work”
My last post about the good and the ugly of the Update Budget Lines feature had a continuing theme to it. I was telling the story of the client who mass updated 650+ projects with a new cost category only to find the budget sources set to Specific didn’t get populated with the default “specific” GL account.
What I didn’t get into was HOW they found the problem. I built some integrations for them for Misc Logs, which they’ve been using for a while now and having no issues with. It’s been a huge timesaver for them, and they love it. Great! So, fast forward to how they found out they had an issue was during the Misc Log import and posting. The problem was, eConnect didn’t fail and alert them of the problem with the missing accounts, it allowed the creation of the transaction without GL distributions and they posted it without thinking to check! Uh oh x2!
This article is explaining the issue, another possible bug, in Project Accounting Misc Log Entry eConnect node (not a problem with Misc Logs themselves).
Continue reading “Project Accounting: Misc Log eConnect import issue”
The other day a client asked me if there was a way to mass-add a new cost category to all projects at once. I actually didn’t know there was a new function to do this starting with GP 10, but a quick google search resulted in a post from Mark Polino describing this exact thing.
Wow. That doesn’t happen every day… I was thinking of the alternatives I would explain the client, but was really happy to see this added functionality.
Until… today, after the client used the new window, and rolled down a new cost category to every project they have, they found a problem. Uh oh!
This particular article relates to the Project Accounting module in Dynamics GP, and the Update Budget Lines window under the Routines menu.
Continue reading “Project Accounting: Update Budget Lines – the good and the ugly”
This is a repeat of an article I wrote in November 2011 with updated information.
Issue #2 in that blog was regarding permissions during the Generate Cheques routine and the message “There is an error in the Transmission Header – Incorrect Length”.
At that time, the fix seemed pretty obvious and it worked during testing on Windows 7 machines. I wrote about it, forgot about it, and moved on. Months later I learned the client doesn’t use Windows 7 on the machines that they use payroll for (those machines happen to be older Windows XP machines) so the error never came up again and I had completely forgotten about it.
Continue reading “Canadian Payroll – Transmission Header Incorrect Length error”
What I’m posting today is hopefully of use to someone out there who runs into this same problem. Admittedly it’s rare but it took me a while to find the answer.
In this case, “I” didn’t find the answer, I found it buried in a community forums post from Sivakumar, one of the Microsoft Dynamics GP MVPs.
Continue reading “eConnect, GL Transactions & Multicurrency”
Recently, a client of mine experienced a couple of weird things when we started to configure another Dynamics GP company for them with Canadian Payroll and Project Accounting in action. One of them is definitely something to look out for if you use the Canadian Payroll import processes; the second is more of a head-scratcher type of error where you don’t know what the real problem is.
I call these things “gotchas” – I’m not sure that translates into all languages but generally means to me at least, something that “GOT” me, that I wasn’t expecting or didn’t think to look out for.
Continue reading “Some Canadian Payroll & Project Accounting gotchas!”