SBX - Finance Heading

Microsoft Dynamics GP January 2018 Hotfix has released!!

Options

I have to be careful in my wording now as we have the YEAR 2018 and Product ID of 2018, wow we make it confusing!!

There is no slowing down right? US Federal tax updates released (within 4 business working days of announcement!!), Year end for US and Canada completed and now a January Hotfix too? Let's just pile it on.

The January hotfix is a mixed bag of fixes, and the FIRST Microsoft Dynamics GP 2018 patch. Review the below changes by version and determine if you need to install it based on your business. Since we are releasing a "patch" we might as well put some critical fixes in there as well that our customers need. I have those listed below by version.

Remember as always, these are all inclusive updates, so you can just install the latest and you are patched to current. The January Hotfix will be translated to Spanish and French.

-You may experience slow performance when you click Inquiry>>Purchasing>>Transaction By Document. Review this blog on new feature.- All issues fixed on the GP 2016 list below are included in GP 2018 as well.

Microsoft Dynamics GP 2016 (version 16.00.0675) (Includes GP 2016 R2, US and Canada Year-end, and all prior patches)-If you installed the 2017 year-end update and create the year end wage file without having Human Resource installed, you will receive an error messages for each employee during creation of the payroll year-end file.-You may receive this error when you create the year end wage file UPR_Year_End_WORK_Other failed. A record was already locked-Canadian Payroll -Quebec Tax Changes, RL-1 form and T4, T4A XML changes (see notes area for complete list)- Your ACA information may appear incorrect for employees that were employed multiple years for your company- You are unable to add new columns to existing Analytical Accounting SmartLists in Dynamics GP 2016 R2 or later & columns with special characters result in "excel found unreadable content" error when list is exported to excel.- Posting a GL reversing entry to a historical year with P&L account, where it reverses in the new year has incorrect SEQNUMBR in the GL20000 and incorrect ACTINDX in AAG30001 on reversing 'GJ' entry and 0% in AAG3000-Upgrade error CO00104 set BusObjKey = replace(BusObjKey,'0\PM\Payables Transaction History','0\PM\Payables Transaction') where BusObjKey -Encumbrance - Unable to print a PO when you cancel a line on a PO-Purchase Requisition Entry, Inquiry, and navigation list handle cancelled lines on Requisition differently with encumbrance. -The Requisition cannot be purchased as Encumbrance Management Pre-Budget invalid-When PO Workflow is enabled, the Encumbrance Status is getting set to a 4 (Pre-budget) after making changes to the PO and you are unable to encumber.-Purchase Order Workflow Approval will cause Encumbrance data problems when the PO is going through the workflow approval process-When two users simultaneously submit a document into a workflow with multiple approvers at the same time, one of the workflows will either go to the workflow manager or only be assigned to a portion of the approvers. -You may notice duplicate payments with simultaneous use of the payables select checks window, warning was added to the user.-Payroll Mask Social Security settings over-written when you install an update (UPR40203 table).

-If you installed the 2017 year-end update and create the year end wage file without having Human Resource installed, you will receive an error messages for each employee during creation of the payroll year-end file.-You may receive this error when you create the year end wage file UPR_Year_End_WORK_Other failed. A record was already locked-Canadian Payroll -Quebec Tax Changes, RL-1 form and T4, T4A XML changes (see notes area for complete list)- Your ACA information may appear incorrect for employees that were employed multiple years for your company-If you are using Web Client, remember to patch it as well, updated certificate.

Microsoft Dynamics GP 2013 (version 12.00.2230) KB4073323

(Includes US and Canada Year-end, and all prior patches)

-If you installed the 2017 year-end update and create the year end wage file without having Human Resource installed, you will receive an error messages for each employee during creation of the payroll year-end file.-You may receive this error when you create the year end wage file UPR_Year_End_WORK_Other failed. A record was already locked-Canadian Payroll -Quebec Tax Changes, RL-1 form and T4, T4A XML changes (see notes area for complete list)- Your ACA information may appear incorrect for employees that were employed multiple years for your company

-If you are using Web Client, remember to patch it as well, updated certificate.

We are upgrading from GP2013R2 US Yearend (KB4046335 version 12.00.2198) to GP2015R2 the most recent version. Our company is in U.S.

What is the shortest path to upgrade?

Can we upgrade from GP2013R2 US Yearend (KB4046335 version 12.00.2198) to the most recent version of GP2015R2 (KB4073325 version 14.00.1100) directly by installing it and then running GP Utilities? Or do we have to install the GP2015R2 RTM, then intermediate service pack/hotfix greater than 14.00.0983 **, and the most recent version of GP2015R2 (KB4073325 version 14.00.1100), then launch GP Utilities?

On Microsoft CustomerSource there is a confusing comment:

“**To install the 2017 US Year End update, you need to be on 12.00.2104 or later or 14.00.0983 or later. Once you install the 2017 US Year End update, you cannot upgrade to Microsoft Dynamics GP 2015 or Microsoft Dynamics GP 2016, until the 2017 Canadian Year-End Update is released, target release middle of December 2017.”

Hi Terry. As of January 31st, 2018, I am unable to download the GP 2018 hotfix. The page doesn't even come up when I try to get to it in Partnersource. Using the link here gets me to the Service Pack, Hotfix, and Compliance Update Patch Releases for Microsoft Dynamics GP 2018 page, but clicking the download link only give me a 503, service not found error. Was it pulled?

Terry - I am experiencing an error when exporting an existing SmartList to Excel similar to the error mentioned in the fix for GP2016R2 (- You are unable to add new columns to existing Analytical Accounting SmartLists in Dynamics GP 2016 R2 or later & columns with special characters result in "excel found unreadable content" error when list is exported to excel.) However, we do not use Analytical Accounting. I only have the problem with Excel 2016. Excel 2013 works fine. Will this fix take care of this problem too? My error is "We found a problem with some content in 'file name'. Do you want us to try to recover as much as we can?" When I click "Yes" the dates are showing =DATE(2017,1,4) in the field and it won’t let me format it. This is mainly happening on SL that I have moved columns.