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”
You can file this under “better late than never”! Our annual deadline is coming up very quickly, as March 31st is the last day you can enter contributions if you are up for renewal in July 2019. For most of us, that is a 1 year period of April 1st to March 31st but with the monthly MVP awards, there are some who have a longer than 1 year first period before renewal. I know I had a longer period last year for my first renewal…
I have had a change of heart since writing this previous post, about how I enter my contributions. In that post, I indicated that I would enter 1 summarized entry for the year with total blogs written to keep things simple. I realized during this past week’s MVP Summit, having had various conversations with product teams, that they prefer details. So, I am now uploading one contribution per blog post and each one has the appropriate categories of contribution on them. I had not done this in the past because the amount of entries using the website to enter them was going to take far too long to be worth it. I wrote 75 blog posts last year, there was no way I was going to put them in individually!
Then I started to play with the PowerShell commands via the API and I’m now a convert. This post is about how to use the MVP API via PowerShell and upload a CSV file with your contributions.
Continue reading “Mass-uploading MVP contributions”
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”
Last week, I was asked if I knew of a quick way to update the Basic Personal Exemption amount in Dynamics GP Canadian Payroll. It’s not the first time I’ve been asked as it’s relatively common for an “oops” on the CPY Year End Close routine to either forget to update the personal exemption amounts or that somehow the wrong amounts are in there. So, today’s #TipTuesday is a short one: what’s the quickest (& safest) way to update this if it was wrong on multiple people?
Continue reading “Mass Update CPY Basic Personal Exemption”
Today’s #TipTuesday is a security tip to help you identify what exact permissions the SQL fixed database roles have, that start with rpt*. If you’re granting access to some of your windows users or groups, you want to know what they can get into, right?
The purpose behind the rpt* roles is generally for SSRS (SQL Reporting Services) reports that ship with Dynamics GP since users running those reports are outside of GP, not tying into GP permissions. There are plenty of other posts out there about GP & SSRS, so I am not going to get into that here. Instead I am going to show you a SQL query I’ve used to see what permissions are granted to what role, login, user or group in SQL.
Continue reading “What’s included in those SQL rpt roles?”
Today’s #TipTuesday is too late for 2018 filings but hopefully those this applies to will file it away for next year. The post is as a result of a question from a consultant who works for one of the Dynamics GP VARs in the Toronto area, whose client asked how to get 1 XML T4 file for multiple employers.
TL;DR version: it does that out of the box although the UI doesn’t make it seem like it would! Since some people may stumble across this post and use other ERP systems, this post is specific to Dynamics GP and the Canadian Payroll module.
Continue reading “Cdn Payroll T4 XML & Multiple Employers”
(At least I hope it’s the end, LOL!). Here are the various parts to my mini-series so far, which is the story behind all of this (part 1), the technical deep dive into the SQL query (part 2), a bit about namespaces in the FOR XML (part 3) and finally a bit about validating an XML file against an XSD schema (part 4).
So, what is this post about? This is taking a step back to describe the process itself. The part 1 story tells you what I’m doing, and ultimately I am all about the process. It’s one thing to create some code in order to create an XML file, but ultimately the best solution for an ongoing, repeatable process is to think about the end to end steps from the point of view of the user. This is about the “solution” that I created, which may give you some ideas on either the thought process behind it, or ideas on how to mimic the same thing yourself for a process of your own on something else.
Continue reading “Fun with XML, the end”
The last of the “technical” parts of this mini-series is about how to validate an XML file with a parser, against an XSD schema. This would complete the list of things I learned in this journey to create a T5 XML file, that I didn’t know before I started.
If you’re interested in the previous parts, part 1 is the story behind all of this, part 2 is a deep dive into the SQL code and syntax for the query, and part 3 is about getting the namespaces correct on the XML file.
Continue reading “Fun with XML, part 4”
The fun continues! Today’s post is about the namespaces. I was unable to figure this out for the longest time and ended up giving up, manually pasting in the values I needed for submission. It was only in prepping this post that I came up with a way to get the namespace attributes in the right spot.
If you are interested in the entire journey, check out part 1 (the story behind this) and part 2 (deep dive into the technical details of creating the XML in SQL).
Continue reading “Fun with XML, part 3”
It seems from searching for this in various forums that other people had the same issue I did: using WITH NAMESPACES seemed to then put the namespaces in every element parent tag, where I only want it on the Submission tag. Here is how I worked around it and I can only assume it’s a “workaround” not a recommended way of doing it. It works so I’m going with it! I hope this helps someone else out there.
Today’s post is a continuation of the mini-series I started on Feb 28th. You can read the first part here if you’d like, which contains the story behind this. In this post I’ll be getting into the technical details on what I learned.
This is about the guts of the XML itself, in SQL, where I ended up writing this procedure. First, before I get into the details, I wanted to reference this Stack Overflow post that was the single most useful post and example for the work I did. The person who posted the example, Ryan, also laid out a very simple temp table structure so I literally copied that code and pasted it into my test SQL server and played with it to understand it.
Continue reading “Fun with XML, part 2”