It must be bug month for me, as I have another issue. One is reported as a bug – kind of – and the other, reading between the lines, will not be considered a bug when all is said and done.
A client of mine had a great question for me last week on the ROE (Record of Employment) form that I couldn’t answer off the top of my head. I took the opportunity to research and test to answer the question and figured it is not an uncommon question, so I may as well share the info.
Before I begin, I am not a payroll guru, I simply understand how the payroll modules work in Dynamics GP. This is not meant to be a “how to complete your ROE” form article. I worked for a few years with an actual payroll guru, who in her own words, could make Canadian Payroll sing! (RW, you know who you are!)
I’m not sure why, but I always seem to find the really obscure bugs in GP, the ones that really don’t affect many others. I guess it’s called a gift. 🙂
Today, I found another one that affects GP10 (although apparently has been resolved – I can’t verify that yet) and a slight variation of the same for GP2010.
A very short off-topic article. When I first started blogging, I thought weekly posts was a good goal, and it seemed pretty easy to keep up with. I had a long list of things I wanted to talk about at some point, no shortage of ideas! I was set!
All was good until I went to the Tech Conference in Fargo in March… then I started writing a blog each day about my experiences. So much information to talk about, so little time! Upon returning home I had so many ideas I didn’t know where to start, and didn’t write much at all. And then time has quietly slipped by…
What usually is a typical service pack install client visit started off on the wrong foot. I am installing SP2 for GP2010 plus related hotfixes for a client, and the last time I was here was in January for the year end tax updates. While I was doing my usual preparation, before I even started the process of installing anything, users started reporting warning messages keeping them out of GP.
I write this with a little embarrassment at the solution to a problem I had. Earlier this week I renamed a server I’m using for GP2010 to prepare for a new network and improve my network naming conventions. I’ve changed server names before at clients and the steps and places you need to make updates are pretty straight forward, at least for vanilla GP. There are other complications when you get into web services and other things where the configuration is not strictly within the application.
At long last I’m back, and aim to get back to regular weekly (if not more frequent) blogging!
First topic, last week I installed GP2010 SP2 (aka R2) at a client site and all was fine. That is, until I was doing some unrelated work in Report Writer, and was getting an error message when coming back into Dynamics GP.
I had some trouble finding this specific error but did find a post on the partner technical forums with the same problem, from a couple of months ago, that had gone dormant. I updated the post with my information, adding to the original poster’s info, and it turns out it is indeed a bug.
I noticed Microsoft posted a date extension on Partnersource to obtain the new certification requirements. It was posted on April 1st, so in light of that being April Fool’s Day, I didn’t want to get sucked into some bad prank and looked again today at the information.
Well, the joke’s on me, it’s real! The original deadlines were to be this coming May 1st, now it’s been moved to October 1st. For me that is great news, the only thing better would be the elimination or reduction of some of the minimum requirements, like say SQL exams, multiple people or minimum revenues.
For customers (& sometimes for partners too), the changes are not always clearly communicated. Most customers have no idea of the changes and if they are affected.
Is it me or is getting support sometimes like pulling teeth? I’ve had a couple of experiences lately which remind me of why I am in this business and why my clients are so appreciative of the way I deal with them and respond to their issues. The reminder for me is NEVER to let my clients experience this with my firm – no one deserves it and even more importantly no one deserves to pay for the privilege!
Yes, it’s time for another small rant…
Today is day 3 in Fargo, and the majority of the day is wrap up and some chances for the vendor sponsors to present their wares. The room is emptying gradually as the day progresses as people are heading to the airport to catch their flights.
This is mostly some observations of the overall conference and a wrap up of my own.