Share
Report
1,582In the near future I will be helping someone upgrade a development dictionary from GP 2013 R2 to GP 2016 R2. The environment does not have any source code repository, so I am writing today to explore options for a successful upgrade.
The help document for Dex Utilities states:
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.
So I believe that option is not viable. I am interested in why that utility can no longer be used for this if anyone has background there.
Setting up a Generic provider in Source Control Options:
I feel the next easiest option would be defining a Generic provider in Dexterity. I have some assumptions about that I would like to ask about.
- This will not provide version control, but that should not matter for this process.
- It will allow us to check in the dictionary resources - pointing to a compressed 2013 R2 dictionary in the Original Dictionary field - which will simply store them as text files in a folder on the drive.
- Then we can pull those resources "down" into a compressed copy of a 2016 R2 dictionary - pointing to a compressed 2016 R2 dictionary in the Original Dictionary field - and that should give us a proper upgrade.
- We always want to use an Index file. Is there any issue with doing that with a Generic provider?
I feel this should be obvious, but I have always done this process with either Visual Source Safe or Team Foundation Server.
*This post is locked for comments
All responses (
Answers (
