Today’s #TipTuesday post is one for those who modify reports in Report Writer (mostly) or anyone who has an alternate Dynamics.set file they wish to launch in their Dynamics GP environment.
A quick review of the terms here: the Dynamics.set file is a launch file that displays the # of products/dictionaries installed on a given workstation, the list of products (product # followed by product name) and then the pathnames to the Code, Forms and Reports respectively for each of those dictionaries, in that order. Back in 2010, I wrote a series about Report Writer and the first post was some detail around the Dynamics.set, how to read it, etc.
Continue reading “Launching GP with alternate Dynamics.set file”
This wasn’t going to be a “Tip” post but it’s Monday night as I write this, so it’s now becoming this week’s #TipTuesday. Funny how deadlines work! 🙂
Late last week, I was working on some upgrade tasks as my firm is going through an upgrade from Dynamics GP 2013 to GP 2016. One of the tasks on my checklist was to review the Unassigned Security Report for new features and update security roles as needed. However, I ran into an issue.
Continue reading “Unassigned Security Report & Superuser roles”
Today’s #TipTuesday post is another Web Client/User Setup post. This one is a bit simpler than my last few, and it’s really just explaining what the Web Client User Only tickbox is for and what happens if you mark that on a user that already has a SQL login.
Continue reading “What does Web Client User Only do?”
Here’s my next #TipTuesday post, which is somewhat of a follow up on another post a few days ago about Web Client & Account Level Security. In that article, I described a couple of bugs that are really authentication related that prevent using Account Level Security (ALS) in the Web Client. That bug is predicated on one assumption: that you’re using the default Windows authentication to log into Web Client.
Continue reading “Forcing a SQL login in Web Client”
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.
Today’s the next instalment in my #TipTuesday series. This tip is about the home page in Dynamics GP.
Wouldn’t you know it? I was trying to think of what I was going to write about for today’s post and a user had an issue with their home page. It was stuck. They couldn’t add or change the panes in it anymore, and the one pane that was visible was maximized without the little icon to shrink it back to normal size. I’ve seen this at other clients too from time to time and have no idea what causes this, but it’s random and annoying!
Here are a couple of ways to fix this issue.
Continue reading “Reset Home Page”
Today’s #TipTuesday is more of a “PSA” (public service announcement) than a usable tip. A question on the Dynamics Community forums reminded me that it’s not obvious that this particular window only supports your Functional currency.
Continue reading “Miscellaneous Check doesn’t support multicurrency”
Today’s #TipTuesday post is about Dynamics GP Report Options windows. In most reports in Dynamics GP, there are options windows for handling parameters for reports, whether that be inputting a range of customers, GL accounts, vendors, transaction references etc.
Over the years, I have repeatedly seen examples where customers have put in restrictions that are redundant: an “A to Z” type of restriction. My guess is the user thinks they *have* to put a restriction of some sort in the window for the report to work. However, it doesn’t work that way…
Continue reading “Unnecessary restrictions in report options window”
This is another post in my #TipTuesday series. Today’s topic is a commentary on currency IDs as well as a tip on currency symbols.
I doubt everyone will agree with my thoughts on the items below as there are different approaches to configuring Dynamics GP. I think this also has elements of an “it depends” situation whether it makes sense for your organization or not. In any case, here is my take on currency setup & symbols and a couple of my tips I follow when configuring currencies.
Continue reading “Currency symbols in Dynamics GP”
Today’s #TipTuesday is another multicurrency tip. This is a simple one but I have still seen many customers with transactional errors simply because the user’s settings are such that it’s easy to mistakenly enter a transaction in the wrong currency.
If your Dynamics GP environment doesn’t have multicurrency enabled, this post is of no value to you! However, for everyone else, when you transact in another currency, this tip may be useful and lead to fewer errors in data entry or analysis.
Continue reading “View options for multicurrency”