Frequently Asked Questions
Here are some of the most frequently asked questions in regard to NavRepository:
- Why would I need a local repository for the Navision objects?
- How could the local repository help for the NAV integration with SVN or CVS?
- What kinds of NAV databases are supported?
- Are there any pre-requirements for NavRepository to run?
- What is actually saved into the local repository?
- Are there any options for synchronization of objects?
- Does NavRepository work on a 64-bit OS?
Why would I need a local repository for the Navision objects?
MS Dynamics NAV is a very well featured and useful system for the end-users, but sometimes it is a bit "surprising" for the developers. It is easy to unintentionally overwrite an already modified object without a possibility to revert the changes back. It is also a bit tricky to exchange only the modified objects with other developers or end-users. Navision provides no way for integration with version control systems. Keeping a local repository of Navision objects would help you resolve these and similar problems related to the development and maintenance of the Navision objects.
How could local repository help for the NAV integration with version control systems, such as SVN or CVS?
The local repository, created by NavRepository is designed in a way, to be easily accessible by version control systems, such as SVN or CVS. This way the modifications of the local Navision objects could be easily propagated to multiple development locations or to multiple end-users.
What kinds of NAV databases are supported?
Currently NavRepository can work only with NAV-databases based on MS SQL Server. Native Navision databases are not supported by the current version.
Are there any pre-requirements for NavRepository to run?
In order to run NavRepository, you must have an operating system of type: Windows 2000 SP4, Windows XP, Windows 2003, Windows Vista or Windows 2008. For the older Windows versions (Windows 2000, Windows XP, Windows 2003) you would also need to install the Microsoft .NET Framework version 2.0 or higher, if not already installed.
When the NavRepository setup starts, it first checks for the .NET Framework availability. If the framework is not present, it suggests to you to download and install it.
What is actually saved into the local repository?
Into the local repository are saved the BLOB references of Navision objects, as well as the textual object definitions - the source code of each object. The BLOB references are binary compressed data files containing both the object definition and the compiled object.
Are there any options for synchronization of objects?
Yes. Take a look at the View menu on the main screen in order to check or switch these options.
You can synchronize only the database objects with Modified flag turned on or both modified and unmodified objects. You can choose whether to synchronize the table-data objects or not. You can opt whether to synchronize the textual object definitions (the object's source code) or just the BLOB references.
Does NavRepository work on a 64-bit OS?
Yes and no. NavRepository itself as a managed .NET application works on a 64-bit OS. The problem is that it uses the COM-interface of Navision to move the textual object definitions from Navision database to the local repository and vice versa. This COM-interface doesn't work correctly under 64-bit Windows systems. This results in the following message: Could not connect to the Navision's COM server. If you prefer not to synchronize the object definitions, please turn off the option "Sync Object Definitions (as Text)".
The solution at the moment is: when possible use NavRepository (together with NAV Classic Client) on a 32-bit mashine. These application could be still connected to the database residing on the 64-bit mashine.