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.
Do you have trouble finding the right G/L account to use when you enter transactions? Do you frequently use the same G/L accounts on your day to day transactions and have the key them in or look them up each time? Have you recently changed your G/L account numbering and can’t remember the new account numbers? Aliases may be useful to you if you answered yes to any of these questions!
How many times have you posted something in Dynamics GP on the wrong date because you forgot to change it? Let the User Date be your best friend!
Continue reading “Let the User Date be your friend!”
Here are few quick and easy tips for you keyboard lovers when it comes to dates inside Dynamics GP.