Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Easy upgrading/merging of NAV developments
Miklos_Hollender
Member Posts: 1,598
I think many of you know this, but maybe somebody does not, so:
If you open two Navision databases (one local, one server f.e. you cannot open two local ones without installing a second client), then copy-paste works very sophisticatedly: copy-pasting a button, menu item, or a function in the View/Locals/Functiobs carries the local variables, the code, and also copy-pasting a table fields carries the locals and the code.
Therefore, to make your developments easy to merged into upgraded databases, you just write a short document listing all the new objects to be imported into the new version, and a very simple guide for modified objects such as:
-T36: copy-paste fields 50012-50014
- F42: create tab Blahblah and copy-paste all the fields and buttons on that tab
and then upgrading will be very easy.
A typical upgrade process would be somethink like this:
- take a local FDB of the standard version of the new version
- import the new objects, copy-paste the changes of the standard objects by the guide you written, test it
- make a backup of the old database and stop the server of course
- import ALL objects of this local database
- run Upgrade Toolkit to upgrade the data. Well, this is where you can have problems. Basically the upgrade toolkits are for the case when the database structure changes in the new version, like there are new fields, and these toolkits change your data to fit the new fields/tables. Maybe the toolkit does not fit perfectly to those changes you made to fields/tables, to this is the only point that can be hard - test it, look at the code, change it to reflect your changes to tables/fields etc. Or just look at what the toolkit does, and copy and run that part of it that's relevant to the functionality you are using.
If you open two Navision databases (one local, one server f.e. you cannot open two local ones without installing a second client), then copy-paste works very sophisticatedly: copy-pasting a button, menu item, or a function in the View/Locals/Functiobs carries the local variables, the code, and also copy-pasting a table fields carries the locals and the code.
Therefore, to make your developments easy to merged into upgraded databases, you just write a short document listing all the new objects to be imported into the new version, and a very simple guide for modified objects such as:
-T36: copy-paste fields 50012-50014
- F42: create tab Blahblah and copy-paste all the fields and buttons on that tab
and then upgrading will be very easy.
A typical upgrade process would be somethink like this:
- take a local FDB of the standard version of the new version
- import the new objects, copy-paste the changes of the standard objects by the guide you written, test it
- make a backup of the old database and stop the server of course
- import ALL objects of this local database
- run Upgrade Toolkit to upgrade the data. Well, this is where you can have problems. Basically the upgrade toolkits are for the case when the database structure changes in the new version, like there are new fields, and these toolkits change your data to fit the new fields/tables. Maybe the toolkit does not fit perfectly to those changes you made to fields/tables, to this is the only point that can be hard - test it, look at the code, change it to reflect your changes to tables/fields etc. Or just look at what the toolkit does, and copy and run that part of it that's relevant to the functionality you are using.
0