Today’s #TipTuesday is a post about Office 365 and Dynamics GP and is specific to email functionality such as emailing Purchase Orders, EFT Remittances and Sales Documents. Rest assured that most other functionality other than email seems straight-forward and works no matter what (like exporting from Smartlist). (At least that’s my experience although there may be exceptions I am unware of!)Continue reading “Dynamics GP & Office 365”
There’s no #TipTuesday today since I had website issues over the weekend and was unable to access it to prepare something. So, this will be a form of a tip in lieu of another topic!
There will be no mid-year tax update for Canadian Payroll for Dynamics GP this year, zippo, nada, zilch! Imagine that, not a single jurisdiction has a tax change this mid-year. That’s got to be a first!
So, enjoy your July 1st without a tax change!
Today’s #TipTuesday isn’t a technical tip, it’s more of a business tip. I’ve written this to be specific to Dynamics GP, although what I describe may apply to other applications and software licensing. I have not worked with licensing on any other ERP packages to know if this might be a general rule of thumb or not.
If you’ve been using Dynamics GP for any length of time, it might be worth revisiting what you’re registered for and have paid for, module/functionality-wise. It’s probably worth taking a look at this every couple of years post-implementation, particularly if you paid for things up-front with the intention of phased implementations later. Every year is probably too frequent, but every couple of years allows you time to evaluate if your master plans have changed, if you still plan to implement what you thought you would at the time of purchase.
The math works out that, on average, every 5 years you are re-purchasing your Dynamics GP software (based on a rough average of 20% annual enhancement from ISVs). This doesn’t apply to subscription-based licensing, which is paid by the month, but the vast majority of users of Dynamics GP are not on subscription licensing (or that would be my guess).Continue reading “Are you using what you’ve purchased?”
Today’s #TipTuesday post is about troubleshooting an issue with the My Reports home page area/pane and how to remove SmartList favourites from there. The specific scenario here related to favourites that were “stuck” in MyReports after an upgrade to GP 2013 a few years ago. I was reminded of this when I saw this post on the Microsoft Dynamics community forum and someone asked me if I kept the scripts I used to fix this issue.Continue reading “SmartList stuck on My Reports pane”
Today’s #TipTuesday is a bit about the “Originating” fields in SmartList, what they are and what you may find in them. These fields are found under the Account Transactions SmartList (under Financial) and in certain circumstances, you will be able to extract *some* subledger information from your G/L to supplement your account analysis.Continue reading “Originating fields in SmartList”
Today’s #TipTuesday post is yet another integration-related post. In my case, it’s about Payables Transaction Entry and distributions doubling up. This tip will (or should) also hold true for other eConnect nodes that have optional GL distributions as most behave in the same default manner I describe below.
I was building a Payables Transaction integration for the first time in a long time. In my case, I am passing in GL distributions so I was mapping both the “PM Transaction Insert” node as well as the “PM Distributions” node. All was going super smoothly and the integration was a success, until I looked at the resulting transaction!Continue reading “eConnect Distributions: Double Trouble?”
Today’s #TipTuesday title is a little obscure but it’s 2 tips in 1! I’ve been building some integrations lately, as I alluded to in my last post. Today’s tip, and next week’s tip, are all coming out of some things I ran into today that gave me some great topics to share! Woohoo!
This tip is about eOne Solutions’ SmartConnect again, and while I am integrating into Dynamics GP ultimately, this tip is purely about a quirk with SmartConnect that is easy to miss.Continue reading “SmartConnect, Variables & Quotes”
Today’s #TipTuesday is about one of the many things this error message could relate to, and it’s in the context of Dynamics GP and SmartConnect/eConnect integrations (not development, where it can also occur regularly for many other reasons). This error came up when I was attempting to preview my data in the Data Source section of the SmartConnect map and I couldn’t move past it until I figured out the cause.Continue reading “Object reference not set to an instance of an object”
Today’s #TipTuesday comes about from a question on the GPUG forum about Asset tags and an issue a user was having with asset numbering not tying back to the asset tags (getting out of sequence I believe was the issue).
This isn’t about that specific piece but a more general tip around Asset ID numbering vs. Asset tagging and use of the Asset Label field. There is no right or wrong answer here, but I do lean towards utilizing the Asset Label field if your organization wants to track the physical asset label of an item, even if you currently use the Asset ID number for that label. More on that after this first section!Continue reading “Fixed Asset Labelling”
Today’s #TipTuesday is actually a tip for those Dynamics GP customers using eOne Solutions’ SmartConnect. Do you have a situation where you want your users to select which company to integrate into themselves, instead of defining a single company on a map? Well, you can… and what I’ll show you also opens up the possibility of integrating to multiple companies in one map, if you want to.Continue reading “SmartConnect Define Company”