Nav Source Control and Data

If you are looking into using source control for your Nav implementation. One of the biggest issues that comes up is dealing with data. Since you now have multiple databases, each developer will have many depending on what they are working on, keeping data consistent across them is difficult. Here are a few ways that might work when trying to sync up data among developers.

Master Data Base

For this to work, you have one database your devs can all access. It always has the most uptodate code. And all the data in it is considered correct. Only finalized changes to the data are made in this database. If the devs or anyone else wants to know what the correct data setup for any part of the system is. They can always refer to this database. Some issues with this is that you are relying on the integrity of this master database. If something goes wrong with it, for example someone changes data to an incorrect setup. Then the incorrect data can spread to other devs and users. Also, it requires everyone to say on top of getting the most uptodate data from this database. Its easy to forget.

XML Ports

Another way to get data around to other developers is to use XML ports. This requires a bit of extra coding as you have to make a port for each object’s data that you want to pass around. ¬†One advantage of this is that you can source control the XML files that the ports create. This way you get a history of data changes. One big issue is that if a table schema changes you have also change the port. This extra overhead can be tedious to developers.


Leave a Comment