Skip to main content

NAV 2013 R2 - How to Create a Blank Database with Blank Company?

Hi all,

It was asked to me a lot of time that how can i create a Blank Database with a Blank company in NAV 2013 R2.

It was so easy till NAV 2013 as the company creation was available in Developer Environment, but with release of NAV 2013 R2 Creating a New Blank Database with a Blank company is changed.

In this article we will see steps to achieve same.



Steps -

1. Create a New Database in NAV 2013 R2 using Developer Environment.

** I Name my Database as Blank Database.


2. In the Recently Created Database i can see only system tables as shown below -


3. Lets see what next i want -

a) Now for creating a company i need Navision Objects, so i opened a Cronus Standard database and exported all Objects.



b) But for importing objects i need a service. (Object metadata sync to SQL via Service Tier.)

c) For Creating Service i need sufficient permission to Service Account on SQL.

4. I will be using network service account to run service, so below are permission required on database.
db_datareader, db_datawriter, db_ddladmin & db_owner


5. Now i will create a service to connect to my Blank database. I will name service as BlankService.


6. Start the Service and start Importing Objects (exported in step 3) in the Blank Database. Do Not Import all objects in one Go. Break into parts as listed below.

a. Import all objects except tables. 
(Filter Import Windows with Type <>Table)

b. Import tables between 1..10000.
(Filter Import Windows with Type  = Table, and ID <=10000)

c. Import Tables between 10000..99008535 
(Filter Import Window with Type  = Table, and ID >10000 & <2000000000)


7. Now Run SyncNav-Tenant Command. How to Run SyncNav-Tenat?

8. Once SyncNav-Tenant is completed we are ready to create a company in database.
How to Create a New Company in Database?


I Named the company as Blank Company.

Let's try to open the windows / RTC Client, and yes we have successfully achieved what we planned for.


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 searchi...

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.