The Developer Update utility is used to transfer third-party resources (all those with resource IDs of 22,000 or greater) from an extracted dictionary back into the Dynamics.dic dictionary. This can be useful if you have an extracted dictionary that you created with the Extract utility, but no longer have the development dictionary you used to create your third-party product.
The Developer Update utility is no longer used to move integrating applications to new versions of Microsoft Dynamics GP. You must now use the source code control capabilities in Dexterity to update your integrating applications. Refer to the Integration Guide for a complete description of this process.
When you transfer an extracted dictionary back into the Dynamics.dic dictionary, it’s essential that you are transferring resources into exactly the same version of the Dynamics.dic dictionary that they were extracted from. If the versions of the dictionary aren’t the same, you will encounter errors in your application, such as incorrect strings being displayed.
When transferring an extracted dictionary, the Developer Update utility can also remake any modifications you’ve made to alternate forms in Microsoft Dynamics GP. To use this capability, you must have an original, unaltered version of the Dynamics.dic dictionary available.
To begin an update, select the extracted dictionary containing third-party resources as the source dictionary and the corresponding version of the Dynamics.dic dictionary as the destination dictionary. Then choose Developer Update from the Transfer menu to display the Developer Update window.
If you made modifications to Microsoft Dynamics GP forms and want those changes transferred to the destination dictionary, mark the Alternate Forms option. A file dialog will appear, asking you to select an editable dictionary. Select an unmodified Dynamics.dic dictionary that is the same version as the dictionary containing your modifications. The utility will use this unmodified dictionary as a baseline to find out what modifications you made.
After a moment, the names of all the forms you modified will appear in the Alternate Forms list. Select each form for which you want modifications transferred and click Insert to display it in the Selected Forms list.
Click the Transfer button to transfer the third-party resources to the destination dictionary and make modifications to any alternate forms you have selected. The Report File Name dialog box will appear. Enter the name and location for the Developer Update Status Report file, then click OK to continue the process, or click Cancel to return to the Developer Update window.
Once the transfer is complete, the status report will be printed to a text file. This report lists all resources that were transferred to the destination dictionary and any errors that occurred while updating alternate forms.
In most cases, your third-party application will work after it has been transferred back into the Dynamics.dic dictionary. If your application can’t locate some resources, you may have to recompile your scripts in the destination dictionary using the Compile Form Scripts, Compile Global Procedures and Compile Global Functions utilities.