Skip to main content

Microsoft Dynamics NAV 2015 / 2016 - How to Create a Blank Database with Blank Company?

Hi all,

This was part of question series #IKnowNav that I started. The reason behind the article as most of the responses answered its not possible.
+
Most of us need to create such database during implementation of a project.

In this article we will see steps to achieve same.

For the Demo I am using NAV 2016 but steps remain same for NAV 2015 also.



Steps -

1. Create a New Database in NAV 2016 using Developer Environment.
** I Name my Database as Blank Database.


2. Next Create a Service for the database or change database name on any existing service. (Don't Start Service).

** I Name my service as BlankService.
** Make sure that service account should have sufficient permission on SQL for database.


3. Export all objects from the Cronus Demo Database based on your requirement.
** I am taking all objects from NAV 2016 W1.



4. Open Blank Database created and From File Menu, Import all objects exported in Step 3.
   Select Replace all from import Worksheet window and select Later in the schema synchronization option.

** If you don't know what these option means you can read here.


5. Start the Service and From Developer Environment (RUN AS ADMINISTRATOR) either compile all objects with schema synchronization as Now with validation or from Tools select sync. schema for all tables - with Validation.



6. Now if we want to run the Role Tailored Client for Blank Database, we will end up with this error.


7. so we need company to start RTC Client. What are our options to create a new company?
   Yes its Powershell or NAV Administration shell.

How to Create a New Company in Database? (Using Powershell)

OR

Open Dynamics NAV 2016 Administration Shell (Run as administrator).


Use Cmdlet New-NAVCompany and select Enter.
Enter Parameters Company Name & Service Name as shown below.
Once you see prompt back that means company is created.


8. Let's try to access Windows Client now.



I hope you will find the post useful and let me know as comments if you have any issues.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searching for the error i figured out the issue was due to - Design change in NA

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.