The following is a list of common problems that can occur during the update process, and how to resolve them. The issues discussed are:
If your application references strings that are no longer part of the Dynamics.dic dictionary, Dexterity will automatically add new string resources to the dictionary. No developer intervention is required.
If your application contains strings that now part of the Dynamics.dic dictionary, a warning will be logged during the update operation. Dexterity will automatically use the string resource in the Dynamics.dic dictionary. No developer intervention is required.
Your application may be referencing resources that no longer exist in the Dynamics.dic dictionary. For example, a field you reference may no longer be included in the dictionary. To deal with resources that have been deleted, you will need to either use a different resource or create your own version of the resource. Then you will have to open each resource (such as forms or reports) that use the resource you created and replace the [Not Found] instances with an instance of the new resource.
If you have chosen to use a new resource that can be referred to directly in scripts, you will need to use the Search and Replace capability in Dexterity to replace all occurrences of the previous resource name with the new resource name. Be sure to compile all scripts after the search and replace operation.
If your integrating application contains resources that have the same name as resources that are now part of the Dynamics.dic dictionary, the update operation will not be able to finish until those conflicts are resolved. How you resolve the name conflict depends on whether you want to reference your own resource or use the new resource in the Dynamics.dic dictionary.
To continue using your own version of the resource, do the following:
In Dexterity, open the development dictionary for the previous version of your application. This is the same dictionary you used in step 5 of the previous procedure.
Check out the source files that contain the resources whose names need to be changed to avoid the naming conflicts.
You must change the names of the resources to unique names that don’t conflict with resources in the new version of Microsoft Dynamics GP.
|
There are special considerations to keep in mind when changing the names of resources in dictionaries that are stored under source code control. Refer to Renaming resources for complete information about renaming resources. |
Check in all of the source files that were changed when you eliminated the naming conflict.
With Dexterity, open the actual development dictionary for the new release of Microsoft Dynamics GP.
An update operation will add all the resources from the source code control repository to the development dictionary. Be sure the following options are marked in the Update From Repository window:
After this procedure, you should no longer receive errors for the name conflicts. The renamed resources from the earlier version of your dictionary will be used.
If you have verified that the new resource included in the Dynamics.dic dictionary is acceptable, and you want to use it instead of your resource, do the following:
The Index File (INDEX.TXT) is located in the Admin folder in the source code control repository. You will need to manually check out this file from the repository, open it with a text editor and remove the entry for the resource that has the name conflict. Check the Index File back into the repository.
Create a new development dictionary by making a copy of an unmodified Microsoft Dynamics GP dictionary from the new release. This “throw away” development dictionary will be used for this procedure, then discarded.
Open the “throw away” development dictionary and perform an update operation. To perform an update operation, point to Source Control in the Explorer menu and choose Update. The Update From Repository window will be displayed. Mark the following options in this window:
Click OK to perform the update operation. Dialogs will be displayed, asking you where you want the error reports printed. We recommend that you print the reports.
Next, the Resources to Update window will be displayed. Be sure all of the items are marked, and click OK. As the update operation is performed, a progress dialog will be displayed.
Because the resource with the name conflict wasn’t included in the Index File, you shouldn’t receive any errors when performing the update operation.
In Dexterity, lock the source file containing the resource that caused the name conflict. For instance, if a field resource caused the name conflict, lock the source file that contains all of the fields.
In Dexterity, check in the source file that you locked in the previous step. This creates a revision of the source file that will not contain the resource that caused the conflict.
With Dexterity, open the actual development dictionary for the new release of Microsoft Dynamics GP.
An update operation will add all the resources from the source code control repository to the development dictionary. Be sure the following options are marked in the Update From Repository window:
After this procedure, you should no longer receive errors for the name conflicts. The new resources in the Dynamics.dic dictionary will be used.