I’m going to file this post under “I’m glad I was late writing it” because in the time that we were notified of a tax change, to the time Dynamics GP tax update code was ready for download, to yesterday’s news that Ontario has cancelled their planned update, things have changed!
This week’s #TipTuesday is about the navigation pane and some very brief tips on personalizing what you see.
Continue reading “Navigation Pane Options”
Today’s #TipTuesday is a recap of the User Preferences window. Last week I was doing some upgrade testing with some staff and I realized some users weren’t aware of how to personalize some elements of their Dynamics GP environment. So, this is a brief recap of what kinds of things are in the User Preferences window.
Today’s #TipTuesday has been on my list for a while and it’s a great resource that many people don’t know exists.
Microsoft has creating a “living” document that has embedded links to SQL views that you can run and tweak in your own Dynamics GP environment to create custom smartlists with. The document says it is for Smartlist Designer but the reality is if you create these SQL views, you can also use them in eOne’s Smartlist Builder if you have the product instead.
I’ve got to admit, this tip has been on my list for a LONG time, and relates to a pet peeve of mine with the configuration of tax schedules. Here is this week’s #TipTuesday for you!
Did you know that you don’t need to have separate tax schedules for a “purchasing” tax and a “sales” tax if they are fundamentally the same? Perhaps this doesn’t happen in the USA but in Canada, most jurisdictions have HST (Harmonized Sales Tax) that are the same whether you are buying or selling.
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.
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.
This is a short post and a weird one! Tonight I was setting up my sample data to test some scenarios for a blog I’m working on. Earlier this week, I came across a situation with the Unassigned Security Report in Dynamics GP and I wanted to write a blog about that. Stay tuned for that!
Cue the testing. As with many blogs I write, there is an element of testing and setting up scenarios to get the facts correct, get the necessary screenshots and generally ensure I’m not missing something when I write. Tonight was no different.
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.
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.