Parent Category: Reports.dic

My buddy Doug Pitcher at Rose Business Solutions has published one of the most hilarious anecdotes I have read in recent months. The subject: the all too famous David Musgrave. If you are reading this article and you are asking "Who is David Musgrave?", chances are you got hit by a bus in the last 5 minutes and can't remember anything or you are way too new to the GP…

Lately I’ve been spending way too much time with Dave Musgrave’s friend – Report Writer. But, I’m learning a few things along the way. Here’s one trick I learned the other day when trying to import a package into RW.

The client has a shared Reports.dic file that each local machine points to. Even though all users were out…

Can I come up for air yet? Talk about a busy month. January is always crazy but for some reason it seems this past month has been extra intense. Now that Year end closes are coming less frequent and 1099's, W-2's etc. should be about done maybe I'll be able to call in sick a time or two and head up to The Big.

One common issue I've seen rear it's ugly head is not being able to print reports after applying a SP or Year End update. GP will either crash before the report is done or will error out and not give you a report. Is it me or has SP's and Year End…

Got the below email from Terry Heley (MBS payroll lead) in conjunction with the new payroll update coming out today. Sounds like a major pain for any SP updates but does sound like job security for Dynamics support people.

Basically, Make sure you update Reports.dic before you do anything. I'd probably export out all reports etc using customization maintenance. Then update the reports using Utilities (I'd probably say a prayer, cross your fingers, commence any other helpful acts of meditation and serenity etc.)

Haven't needed to do this for a SP yet but my guess is creating a new reports.dic file and importing in your old reports after the SP update would be an easier way to update the reports after a SP.

Notice no error messages will be given if you don't do this step other than some probably errors when you run the report. Nice one MBS.

One of the most important and such a basic thing that I learned couple of hours ago is: How to update our Customization's Forms/Reports Dictionaries? Silly, isn't it? For I am supposedly a GP Consultant with 5 years of technical experience. But then, I do not mind admitting with my utmost honesty that, this is what I learned TODAY. And of course, I am contended that at least now I learned it...

I always version the Customizations that I develop, which will be relevant to that of the GP's version. For instance, I alway start with 10.0.0 as my product's version which is for GP 10.0. And it increases with every build, a feature addition and so on.There is this customization which I am involved in for quite some time. And there is a report which is quite a complex stuff and the users always were so satisfied with their own trials with Report Writer and changing the format to their wishes.Things were going on well till the users modified the report. From then on, whenever I install the next version, it would throw this error message (shown below):

I knew for sure that since I maintain a proper versioning, the Reports dictionary for my Customization product should be upgraded to the latest version…