In my last post, I continued on the “know your environment” topic. So far I have 2 parts to that with a background on the elements to be aware of with core Microsoft components of Dynamics GP plus ISV products, where they are modules/functionality within the Dynamics GP client. In this post, I will delve into external ISV products.Continue reading “GP Upgrades – know your environment part 3”
In my last post in this Dynamics GP upgrade series, I talked about getting to know your environment. The importance of understanding some of the moving parts cannot be understated, if you are “in charge” of your environment in any meaningful way. Reading this series won’t allow you to bypass utilizing a partner or consultant for some things, but hopefully it gives you more background to understand different parts of the environment, and perhaps fill some knowledge gaps.
In this blog post, I will continue on the Know Your Environment angle, continuing from where I left off. I covered most of the core Dynamics GP “Microsoft” elements of a given environment but ignored ISVs plus many other parts of the environment to be aware of. Overall this part of the upgrade series may still take more than 2 posts to adequately cover!Continue reading “GP Upgrades – know your environment part 2”
This is the 3rd post in my series about GP Upgrades. Today’s topic is what I refer to as “getting to know your environment”, as part of the planning process around your upgrade. If you are planning an upgrade, it’s important to understand where the moving parts are, and at least to have what I refer to as a “conversational” knowledge of your GP system, even if you aren’t familiar with the nitty gritty details. This is too long a section for one post so I will be breaking it up into smaller pieces.Continue reading “GP Upgrades – know your environment”
Last week I posted the first in a series I am writing relating to Dynamics GP upgrades. This week’s topic is an overview of what the process looks like for many organizations, from the point of view of upgrades I’ve done or been involved with. At the end of this post I’ve included a Context section to further clarify what my background is which will heavily shape the recommendations and approaches I discuss through this entire series.Continue reading “GP Upgrades – process overview”
I’m finally ready to get back into a regular blogging rhythm and will be starting a series around Dynamics GP upgrades. I’ve presented on this topic a few times and what I plan on covering is how I approach and manage upgrades. What this series will not be about are the technical “how to upgrade” aspects. There are plenty of other articles out there covering the actual upgrade process and technical elements, so I don’t feel the need to repeat that here.
I am working with a client on their upgrade now so a lot of the things I cover will be fresh in my mind as they are in the “test upgrade” phase right now, and not “going live” for a few more weeks now. This also may result in the topics being a little bit random, vs. a specific order of events style of posting!Continue reading “GP Upgrade Tips series intro”
Today’s #TipTuesday post is a play on words, an upgrade tip. If you are upgrading Dynamics GP, during your test upgrade phase, consider renaming (slightly) your company names in your test environment.
Every single report you print from Dynamics GP will (by default, at least) have the company name print on it. The vast majority of reports will look identical to your pre-upgrade environment, most times at least. That means you can’t tell the reports apart after you print them out.
So… my tip is to rename my companies. This saves me handwriting on every single report printout which environment I printed this from! Easy peasy!
This screenshot is an example from my current company’s upgrade. We are upgrading on 2 new servers which will be a new production server and a new test server. So, on the ‘future’ production server, all of my companies are renamed with an abbreviated name + “Upgrade P” for production and “Upgrade D” for dev environment.