Happy new year everyone! It’s January 1st, 2011 and, like many of you, I take some time around the new year to look back on my last year and look forward to the new. It’s always fun to take a look at last year’s resolutions to see how you fared a year later. I’m not sure if others do this too, but most of the time the resolutions I wrote the previous year, I don’t look at again during the year! Ugh! No wonder resolutions are not very successful for me!
Last week I sat with a user at a not-for-profit agency. This user is an older semi-retired gentleman who has a fairly strong accounting background, and is supposed to be working 3 days a week. They converted to Dynamics GP in October 2010 after using Simply Accounting for years.
The Executive Director called me to arrange for me to come in due to concerns that her financial co-ordinator had not, at that point, started entering any November activity. He had received what she deemed a lot of support from the folks who implemented them. They were rapidly approaching the end of a quarter (end of December) and she has only recently received October financials.
I have known about the Support Debugging Tool for a while but have never had an occasion to install and use it at a client location.
I took advantage of a recent client upgrade from GP9 to GP2010 to install it on all of the workstations while we rolled out GP2010. It has already paid dividends!
In GP2010, a new feature was introduced to remember the user and company. I’ve seen a few blog posts about this, however I have also seen some incorrect information being posted about this topic which I hope to clear up.
I ran into a difficult situation at a client where we were unable to edit (add new features) to GP2010, unable to uninstall or repair GP2010 and unable to launch GP2010 because of dictionary version mismatches. If you ever have issues finding the references in the registry to troubleshoot installations I hope this may help, that is where I ended up in my quest.
After receiving some positive feedback on my recent customer service article, I thought I would continue with the odd off-topic article (defined as non-Dynamics-GP). I’m certainly finding recently a whole LOT of examples of shall we say “learning experiences” to draw from!
Having recently moved, we are undertaking some renovations to the house over the next little while – some relatively minor, some relatively major. It’s been an eye opener so far in terms of how the various people we have been dealing with run their businesses. While I certainly am far from perfect, I would like to think that I would do things much better than some of these folks given the opportunity.
If you have modified many Dynamics GP Report Writer reports in the past, you will have perhaps found that dealing with text fields is sometimes a little tedious. Here are a few simple tips to help you modify those reports a little faster.
Continue reading “Report Writer series: Formatting Text”
I believe that sometimes companies need to step onto the other side of the counter and view themselves from the customer’s standpoint. I don’t intend to post non-Dynamics GP related things very often but today I had the good fortune of having three incidents worth talking about – two on the negative side, one on the positive side.
My last post was the introduction to dictionaries and launch files for those new to Report Writer (or GP). This post is all about things to keep in mind before you actually venture into Report Writer to start working. It’s rather boring stuff but it’s important to protect your reports from becoming corrupt or damaged due to poor process or lack of understanding.
This is the first in a series of posts about Microsoft Dynamics GP’s built-in reporting tool – Report Writer. However, I am starting with some background that is more general to Dynamics GP before I dig into Report Writer itself. Hopefully some of these posts will add some new tricks to your repertoire or give you the confidence to try modifying a report on your own!
The first two articles contain some background and key information to keep in mind. In future posts I will give you different tips and tricks on some fine tuning, how to make your reports look nicer, etc.