Brandon Jarrett
Forum Replies Created
-
Hey Stephen,
Based on your information, this a dictionary issue and it can cause crashing as well when running reports. Sometimes it takes a specific order of operation as well to correct this.
I would suggest the below:
First, export all your Modified Forms and Reports.
Next, rename the forms and reports dictionaries to be .old.
Set the Synchronization and Initial line to TRUE in the Dex.ini.
Run through the Synchronization Process in GP Utilities.
Imported the Forms and Reports that were exported so they create new Reports and Forms Dictionaries.
Revert the Initial line in the Dex.ini back to false. Synchronization line to change back on its own.
Might need to run through the Synchronization process again once the Reports and Forms are imported.
Repeat for each workstation that you have that is having this problem
As mentioned above, the order that these are done in can change the outcome and suggest the order above.
To add onto this a great test that can be done is to set security back to the core report and determine if the Core Report does the same thing. The reason for this is because the core report comes from the Dynamics Dictionary and not the Reports.dic. If it happens with the core one, you might need to rebuild the GP Code Folder by renaming it and running a repair. This will rebuild the code folder to its default state, and you will need to add your customizations / third parties back in.
I hope this helps!
Thank you!
-
Hey Donald,
Here is what I believe is happening.
Terry Heley, had a workstation that ran this. As we all know, she retired last month. This likely got powered off and will no longer work in the future as Terry is no longer at Microsoft to maintain this.
The approach forward is going to be Manually do this this with either the manual option or running the SQL Script.
Going to be interesting the next couple years now for Payroll with Terry retiring,
Hope this helps!
Thank you!
-
Hey Donald,
I would agree. Thanks for pointing this out.
Looks like the Tax Download from Microsoft might be the previous rounds still even though it says Round 6. In the Overview section, it states that the 2026 Round 6 “Released on 7-29-2026′ contains changes for Georgia and Ohio.
U.S. Payroll Tax Update for Microsoft Dynamics GP | Microsoft Learn — Hyperlink
Down a little the Tax Update Changes shows the Tax Table was updated only for Ohio.
Looking at the Downloads part, it shows the release date of 7-29-2026 and the description says 2026 R6 so it should be the Round 6 we see from the above.
The link below gives us actual details on what was changed for the release and does contain 7-29-2026 release information.
US payroll tax update – Dynamics GP | Microsoft Learn — Hyperlink
This states that the Tax Rate for Filing Status NA, the If over ‘0’ but not over ‘26,050’ the tax rate is 1.6 and Tax Amount of ‘0’. for if over ‘26,060’ but Not Over ‘100,000’ a Tax Amount of ‘416.80’ with a tax rate of ‘2.990%’ on Excess Over ‘ 26.050’. Then we have If Over ‘100,000’ but Not Over ‘And Over’ with a Tax Amount of ‘2627.91 with a Tax Rate of ‘3.4%’ On Excess of ‘100,000’ for Ohio.
Looking at the Tax Tables after updating using the Round 6 from the website, this is not what I am seeing. I am seeing:
Tax Rate for Filing Status NA, the If over ‘0’ but not over ‘26,050’ the tax rate is 1.77500 and Tax Amount of ‘0’. for if over ‘26,060’ but Not Over ‘100,000’ a Tax Amount of ‘462.39’ with a tax rate of ‘2.990%’ on Excess Over ‘ 26.050’. Then we have If Over ‘100,000’ but Not Over ‘And Over’ with a Tax Amount of ‘2673.50’ with a Tax Rate of ‘3.64%’ On Excess of ‘100,000’ for Ohio.
I tried finding the Round 5 Tax Update but cannot seem to find it. My guess here is that these are still the Round 5 Tax Updates and the name just got changed and published round 5 again :).
Georgia appears wrong as well.
I went and compared the Round 5 information for Arkansas changes and these match the documentation for Round 5.
At this point, my assumption is they published the wrong Tax File as the Date in the script for the Tax Update is 6-12-2026.
Until Microsoft corrects this, the changes can be made to the Tax Tables to reflect the new changes for Ohio if needed.
Taxes are just an estimate so imo it’s not a huge deal.
Hopefully they get this correct on the next round.
I hope this helps!
Thank you!
-
This reply was modified 1 month, 2 weeks ago by Brandon Jarrett.
-
This reply was modified 1 month, 2 weeks ago by
-
Hey Seth,
Unfortunately, it appears that the Automatic Tax Update is no longer functional. The assumption I have is because Terry Retired and she had maintained this on a PC she had at her desk. I assume this got powered off when she retired and this process will not work going forward and will need to rely on the manual approach.
The manual approach is just as simple but a couple extra steps.
1. Download the Tax update from the link below.
U.S. Payroll Tax Update for Microsoft Dynamics GP | Microsoft Learn
a. We can see the Ohio update was released in round 6.
2. You can then install it two ways.
a. Open the Payroll Update Method window.
i. Dynamics GP | Maintenance | U.S. Payroll Updates | Check for Tax Updates.
b. Mark the Manual Radial Button and click Next.
c. Click the Folder button and path out to the location you saved the download to and select the folder location.
d. Click Process.
i. One thing to keep in mind is this process only works once per download. If you already ran it and want to do it again, you need to download it again.
1. Not sure why this happens but is an odd thing I have noticed. š.
e. Click Finish.
3. Now you can check the Payroll Tax Setup window and verify the date of the Last Tax Update to verify it was successful.
a. Administration >> Setup >> System >> Payroll Tax
b. This should show 6-12-2026.
4. Here is what the tax tables look like.
I hope this helps!
Thank you!
