Kuntz Consulting Inc. – Canadian Payroll Year End 2013 Tax Updates

Hi, I’m Jen, the owner & chief blogger at Kuntz Consulting Inc. I’m a CGA as well as a Microsoft Certified Professional in the Dynamics GP application. My home base is just Email: info@kuntzconsulting.ca. © Copyright, 2014 

More:
Kuntz Consulting Inc. – Canadian Payroll Year End 2013 Tax Updates

November 22, 2013 · Jen Kuntz · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 76

Canadian Payroll Year End 2013 Tax Updates

It’s that time of year again! Cue the Christmas/Holiday carols of choice in the background please…

Here’s some advance info, courtesy of Terry Heley, on what’s coming in Canadian Payroll for Microsoft Dynamics GP this year.  I’ll update this post once it’s released, or you can watch the applicable page below for updates.  Also, bookmarking the Dynamics GP Support and Services blog page is always recommended!

The anticipated date the updates are available is December 18, 2013.

Update Pages

GP2010 – click here

GP2013 – click here

ROE (Record of Employment) changes

  • Blocks 10, 11 & 12 have had their date format changed
  • Block 15C now needs to be blank
  • Zero Pay Periods now have to be blank

Tax changes for 2014

  • Appears to be the usual, EI, CPP, Federal tax, QPIP, QPP & most of the provinces & territories have changes. I don’t see Nova Scotia or PEI on the list of provinces with tax changes but that could change I’m sure…

Potential Forms/XML changes

These are still under review, in terms of exactly what changes are required. These all potentially have form or XML changes or both.

  • RL-1 
  • T4
  • T4A 

 

See the original article here:
Canadian Payroll Year End 2013 Tax Updates

November 22, 2013 · jen@kuntzconsulting.ca · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 170

How to Display Parent Company Information on SOP documents

A few days aback I encountered a really interesting discussion on the Microsoft Dynamics GP Community forum where the user needed to get the parent customer information on the SOP Blank Invoice Form. I asked myself, “Well, how difficult can that be?”

The first thought around these requests is, you create a table relationship between the Sales Transaction Work (SOP_HDR_WORK) table and the RM Customer Master (RM_Customer_MSTR) table by Customer Number and you get the parent customer ID. In that train of thought you immediately realize that there’s no way to alias the RM Customer Master table back into the table relationship to retrieve the parent customer ID information. NOTE TO SELF: this would be a cool Report Writer feature, but I digress.

Of course, a second alternative is to use VBA, but many customers and partners are wary of implementing a VBA solution, especially when they are considering upgrading to Microsoft Dynamics GP 2013 and taking advantage of the web client. VBA customizations simply do not work with the web client.

As I thought through an alternative, I quickly realized this would be a good fit for the Support Debugging Tool and it’s awesome Runtime Execute feature. As it turns out, the Support Debugging Tool is capable of executing Dexterity sanScript code within the context of any dictionary, but not only that; it provides some really cool templates that save time and minimizes the amount of code an entry level developer needs to create to accomplish a solution. In turn, there are a number of Report Writer API scripts built into the Dynamics application dictionary (DYNAMICS.DIC) to allow third party developers to expose data from their tables onto an existing Microsoft Dynamics GP report without having to write a complex interface to do so.

The Solution

1. The first task at hand is to open the Runtime Execute window in the Support Debugging Tool. Once the window is open, click on the Helper button to open the Insert Helper Function window. From the drop-down list, select template for rw_TableHeaderString.

Insert Helper Function window

Below is the signature for the function as we will use it.

The rw_TableHeaderString function

function returns string sData;

in integer dict_id; Support Debugging Tool Dictionary ID
in string report_name; Support Debugging Tool Script ID to call
in string sNumber; Parent Customer ID field we will retrieve
in integer sType; Not used, we will default to 0
in integer iControl; which piece of data to return

We will use this function to return a string value for the selected Parent Customer ID information field to a Report Writer calculated field.

By clicking OK, the Support Debugging Tool inserts the code to get us started in the right direction.

Helper Code

Very cool! All that’s left now is to add the extra bits of code to retrieve the parent customer information from the RM Customer Master. In addition, we need to make sure that this code executes in the context of the Microsoft Dynamics GP product.

Additional Code

The template function even indicates where our code should be inserted and as you can see this is easy stuff for any entry level Dex developer. All we did here was use the MBS_Number local field as the parameter value that will contain our parent customer ID (to be passed from Report Writer) to get the piece of data we are interested in based on the value that we will supply to the MBS_Control local field (again, from Report Writer). The returned table value will then be stored in the MBS_TableHeaderString local field.

The Support Debugging Tool then goes to action and call its MBS_Param_Set API function to talk back to the Report Writer API script and deliver the values retrieved to it. Isn’t this awesome!

2. The second part of our solution consists of 3 parts really: a) we need to create a table relationship between the Sales Transaction Work table and the RM Customer Master table as this relationship does not exist out of the box, b) We then need to create calculated fields for the pieces of Parent Customer data we would like to retrieve, and c) We need to complete the layout and grant security to the modified report.

I will assume for this article that you are familiar with the processes of creating new table relationships in Report Writer and laying out the new calculated fields and granting security to the modified report. You can always browse the Report Writer manual accompanying your Microsoft Dynamics GP application for information of these processes, so my attention will focus solely on the calculated field.

In this example, I want to retrieve the parent customer name. For this we will create a new calculated field as follows:

a) Create a new calculated field, in this case I will call it (A) Parent Name. The result type of the calculation will be a String and the expression type is Calculated.

b) Since we are using the rw_TableHeaderString user-defined function, we will choose this accordingly:

rw_TableHeaderString

c) Now we have to setup the parameters as indicated by the function signature above. The first parameter we will add is the Support Debugging Tool’s dictionary ID, 5261. We will add this as an integer constant.

Dictionary constant 5261 to call the script we wrote

d) Now we have to call the Runtime Execute script we created, GETPARENTINFO. We will add this as a string constant.

GETPARENTINFO

e) We now need to pass the parent customer number parameter, our default (not used) parameter, and the value number for the field that will be retrieved for the parent customer data, according to how we coded our script above. This is shown below.

Last 3 parameters.

The RM_Customer_MSTR.Corporate Customer Number field is retrieved from the RM Customer Master table which we created via a new table relationship and subsequently adding that table relationship to our report.

The following shows a muck-up of the report layout with the parent customer name calculated field created:

Report Layout

The report should display something like this when run in Microsoft Dynamics GP:

Invoice Layout

Final Notes

The above script could be extended to retrieve other pieces of data for our parent customer, like contact, address, city, state, zip, phone numbers, etc. In this case you will need to add more entries to the case…end case statement above and retrieve the correct table column. You can find more information on the table columns for the RM Customer Master in the Microsoft Dynamics GP software development kit (SDK).

This solution is absolutely compatible with Word Templates and the Web Client. In the case of Word Templates, you will need to export a new report definition file (XML) and import into your template fields. In the case of the Web Client, all the components above are within the confines of a Dexterity application and the Support Debugging Tool happens to be compatible with the Web Client, just as much as Report Writer is. Your modified report should render absolutely fine on the Silverlight canvas control, if printing the standard report.

For all workstations to take advantage of the Runtime Execute script, the Support Debugging Tool must be deployed with the recommended configuration – all workstations pointing to a centralized configuration file, debugger.xml.


The Support Debugging Tool never ceases to amaze me. You can find similar article to this one and more information here:

The Dynamics GP Blogster – Adding Customer Item User Defined Field to SOP Invoice

Developing for Dynamics GP – The Support Debugging Tool Portal

See more here:
How to Display Parent Company Information on SOP documents

November 18, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 191

Web Client Wednesday – Microsoft Dynamics GP Reset User Password not working

Continuing with the Web Client Wednesday series, today I wanted to highlight the fact that the web client is still a work in progress. While a lot of ground has been covered over the past 3 years, the product continues to evolve, and of course, in the meantime there will be little issues here and there that may affect the way you work.

Previous articles in the series:

Web Client Wednesday – Browser Support

Web Client Wednesday – User Interface Differences



Just recently I ran into a Microsoft Dynamics GP 2013 web client deployment case where the advanced SQL Server options are enabled to enforce password expiration. These properties are a part of the Enforce Password Policy options on the User Setup window.

User Setup

When a password expires and a user attempts to log into the desktop client, they are immediately prompted to change their password and the Change User Password dialog window displays to allow the user to enter the old password, and enter and confirm the new one.

Change User Password window

The behavior is different under the web client, however. Whenever a password expires, the Change User Password dialog displays as expected, but in this case, the Old Password field is disabled and the user would only be prompted to enter the new password and confirm.

Change User Password dialog on Web Client 

Microsoft Dynamics GP uses the old password to establish a connection to the database – at this point, the user has not validated their SQL credentials – in order to set the new password. If the old password is not supplied the connection cannot be established, which in turn fails the attempt to change the new password.

This issue has been identified as a bug by Microsoft Support in Fargo and is currently in the queue for resolution. If you are affected by this problem, you are encouraged to open a support case and add yourself to the list for a fix.



For more information on how the password system works in Microsoft Dynamics GP, please take a look at the following articles:

Developing for Microsoft Dynamics GP – Why does Microsoft Dynamics GP encrypt passwords?
Developing for Microsoft Dynamics GP – Microsoft Dynamics GP Application Password System
Microsoft Support – FAQ about the Advanced SQL Server options in the User Setup Window

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

More:
Web Client Wednesday – Microsoft Dynamics GP Reset User Password not working

November 13, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 185

The Dynamics GP Blogster: Web Client Wednesday – Microsoft …

Microsoft Support – FAQ about the Advanced SQL Server options in the User Setup Window Until next post! MG.- Mariano Gomez, MVP IntellPartners, LLC http://www.IntellPartners.com/. Posted by Mariano Gomez at 8:00 AM …. Exchange Rates Feed – Few days back I got mails from many customers reporting that the exchange rates feed stopped working due to an error with the host, the tool was linked t… 17 hours ago 5 days ago. Dynamics Confessions Blogspot.

Read the article:
The Dynamics GP Blogster: Web Client Wednesday – Microsoft …

November 13, 2013 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 80

Tech Tuesday: How to Add an Extender View to a SmartList

This week’s Tech Tuesday article is from our very own support guru, David Youngquist! Dave knows everything there is to know about our software solutions and shares how to add an Extender view to a SmartList.

There are several ways to add Extender data to a SmartList using SmartList Builder, but one method that is often overlooked is creating an Extender view and linking that view using Smartlist Builder. 

Here are the simple steps for adding Extender data to a Smartlist. 

Login to Great Plains as the sa user (only the sa user will have Views as an option)

1.       Click on Views, then click New.
2.       In the Extender View window, give the view a name, and then click the add button. 

3.       Pick “Extender Window” as the type, and pick the Extender window you need to add to the SmartList.

4.       Check off the fields you want to appear in the view.  I would recommend marking all. 
 

 

5.       Click Save on the View. 

6.       Now to go Tools – SmartList Builder – Security – SQL Table Security. 

7.       Checkmark the database you created the view in, and change the type to “Views”.  Place a checkmark in the view that you just created. 
 
 
8.       Hit the OK button to save the security.  
9.       Open up SmartList Builder and open the SmartList you need to add the Extender data to. 
10.    Click on the + button to add a table.  Pick SQL Server Table



11.       Change the list to show “Views”, select your view, and then add it to the SmartList.  Make sure you use a left outer join if you have data in the main table, but there may not be data in the Extender table.  Pick the appropriate key field from the list to link the Extender view to the main table. 

12.       You now will have a SmartList that will display Extender data on it.  
 

 Interested in a demo of Extender or SmartList Builder? Feel free to email sales@eonesolutions.com for more information!

Taken from:
Tech Tuesday: How to Add an Extender View to a SmartList

November 12, 2013 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 224

Business Analyzer New Release is out in the App Store

Readers of this blog might remember that I have been a fan of the beautiful business analyzer application for Dynamics GP for a long time. In fact it has been almost 2 years since I posted my video on a windows touch table – Dynamics GP Business Analyzer on a Windows Touch Tablet.

Meanwhile, the product has received a lot of updates, and its a great fit for Windows touch tablets. A new release came out over the weekend, and if you have not yet tested this application – not is a great time. Ian Grieve has great instructions if you need help installing this app – Installing Business Analyzer R5 From The Windows 8 App Store

CFOHOMEPAGE

Continue reading here:
Business Analyzer New Release is out in the App Store

November 12, 2013 · Jivtesh Singh · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 120