You’re offline. This is a read only version of the page.
35
We are in the process of upgrading from GP 2013 to GP 18.4 (which requires a hop to/from GP 2016). The test upgrade went fine, however we're having trouble with our customized forms (customized reports seem to be fine) and I was hoping someone could confirm the procedure that should take place so that they come over properly.
We had to setup a test GP 2013 and migrate to it first (we needed to apply the latest 2013 SP in order to upgrade to 2016 and couldn't in the live environment for a few reasons). Are the steps below the way this should be done?
1. Copy DYNAMICS.SET, FORMS/REPORTS.DIC to the 'test' 2013
2. Run GP Utilities in 2016, pointing to the DYNAMICS.SET from step 1, process upgrade of forms/reports
3. Run GP Utilities in 18.4, pointing to the DYNAMICS.SET from the 2016 version
The customized forms ARE present in 18.4, but they don't look right. Every distribution window (and their distribution grids) in the system had been widened to accommodate our extraordinarily long account string, and while the grids are widened in 18.4, the windows themselves are not, so a good amount of information on the right hand side of the screens is not visible.
Any advice would be greatly appreciated as we have quite a few screens customized in the fashion, and we would prefer not to have them recreated. Thanks in advance!
Justin,
Next to Roderick's suggestion to get the dictionary updated, I usually take an additional step from the old GP system (in your case 2013).
I always make sure I have a full export of the Forms & Reports as a package file. You can do that from the customization maintenance form.
This way, if something does go right with GP Utilities, I can always re-import them from Scratch, and don't even have to bother at the intermediate upgrade steps.
Step 1: synchronize the Dynamics.dic, Forms.dic, and Reports.dics
If the Forms and Reports dictionaries are not shared, this process should be done on all workstations with the issue.
Test if issue still occurs, if so go to Step 2.
Step 2: Upgrade the Forms.dic, and Reports.dics
If the Forms and Reports dictionaries are not shared, this process should be done on all workstations with the issue.
Step 3: If this does not resolve, then recreating the Forms.dic and Reports.dic should resolve it.
First, verify the location of the Reports and Forms dictionaries on the problem workstation by:
*Copy and paste the path for each dictionary into a document (word or notepad should work just fine). Make sure that you are recreating the Reports.dic and Forms.dic in those specific locations when going through the steps below (additionally, if you have reports and/or forms dictionaries associated with other products listed in this window, you should recreate those as well if you see the same issue when printing those reports – simply highlight the product id to verify ‘where’ each is located):
Next, follow the steps outlined in KB article 850465 to recreate the Reports.dic.
Below is a link to KB Article 850465 How to re-create the Reports.dic file in Microsoft Dynamics GP:
http://support.microsoft.com/kb/850465
Next, follow the steps outlined in KB Article 951767 to recreate the Forms.dic.
Here is a link to KB “How to re-create the Forms.dic file in Microsoft Dynamics GP”:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (