[Scenario] Three different companies

JTPro
Member Posts: 169
Hello all,
I need your opinion and sugestion.
I have a following situation. Three companies in a three different countries. These companies are financially separate, so each of them has to be represented in a Navision as a different company. But there are some common fields, like orders, customers, vendors. Two companies should work with functionality of a version W1 and other one with PL. All employees from all companies is about 70.
My idea is to put Navision on the central server, with functionality of PL version (that includes functionality of W1) and allow all client to connect to the server using VPN or something else. Each company will contain his own licence. Database of course SQL Server. Set some tables common for all companies.
Is it a good idea? Do you think that this might be worked?
I am indebted to you for your answers.
Best regards
I need your opinion and sugestion.
I have a following situation. Three companies in a three different countries. These companies are financially separate, so each of them has to be represented in a Navision as a different company. But there are some common fields, like orders, customers, vendors. Two companies should work with functionality of a version W1 and other one with PL. All employees from all companies is about 70.
My idea is to put Navision on the central server, with functionality of PL version (that includes functionality of W1) and allow all client to connect to the server using VPN or something else. Each company will contain his own licence. Database of course SQL Server. Set some tables common for all companies.
Is it a good idea? Do you think that this might be worked?
I am indebted to you for your answers.
Best regards
Navision Application Version: 4.0SP1
Navision Database Version: 4.0
Navision Database Version: 4.0
0
Comments
-
Technically, it's a good solution.
However, each country has their own localized version of Navision to be compliant with the local tax laws. You'll probably need to take that into consideration as well.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
You can have one database with a common object base, in which case you will have to merge localizations from three countries into one set of objects, and you would have one database to maintain. This has been done (although I don't know for sure for the particular countries in your situation). You can also have three separate databases, in which case you don't have to merge localizations, but you have three databases to maintain.
A lot of this will depend on your preference.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions