Article ID: 894699 - View products that this article applies to.
This article describes how to use an index file and the Microsoft Dynamics GP Dexterity source code control functionality to make sure that the resources that you create maintain the same resource ID in different builds and versions of your code. These resources include items such as forms, reports, tables, and fields.
When you use the source code control functionality that is built into Dexterity, all resources are stored as text in your source code repository. Microsoft Visual SourceSafe is one such repository. These resources are stored by using their names as the unique identifier.
In your development dictionary, the unique identifier is the internal resource ID that is generated by Dexterity. For third-party developers, the resource ID starts at 22,000. Each resource that you add is assigned the next available resource ID for that resource type. Therefore, your resources are typically numbered in the order that they were created. However, if you deleted resources, the resource ID is reused.
When you create a new build, you start by using a copy of an unmodified Dynamics.dic dictionary file. Then, you update this dictionary file to include the resources from your source code repository. During this process, resources are added to the dictionary in alphabetical order, and new resource IDs are assigned to the resources.
The fact that the resource IDs are now ordered alphabetically may cause several issues:
If you have multiple developers who are working on a single project, you must assign one developer as the administrator of the project. The administrator’s role is to create the new builds and to maintain the index file. To create and maintain an index file, the administrator must follow these steps on his or her computer:
For more information, review the "Part 9: Source Code Control" section of Volume 1 of the Programmer's Guide that is included with Dexterity.
Article ID: 894699 - Last Review: July 14, 2012 - Revision: 4.0