You’re offline. This is a read only version of the page.
Hello,
We are currently upgrading from Navision 2013 to Navision 2016. We are going to go live soon and want to merge our two database to have a combined holistic report. They have different localization (US, Dubai/India). We are now paying a global tax.
According to our vendor, doing this is complicated, they will have to make a lot of configurations and treat it as an implementation project.
I want to understand what problems we will face if we combine two database with different localization. Also, what challenges are our vendors talking about? They are really apprehensive to merge the two database, I want to know why?
What are the pros and cons of combining both the database?
*This post is locked for comments
hi,
keep localized db separate like suggested by all people in this post.
Many updates about fiscal requirements in some contries manahed by cumulative updated, different logic and posting structures. different fiscal reports.
use consolidation ore use Power BI to build reports.
Hi Varun,
Your NAV Vendor is right. It is not recommended, and will cost a lot for merging different localizations including Application Code and Data Structure. Consolidation Data as Amol, Ahmed and Manish mentioned is a good solution.
Every country has different localizations and merging those localizations is always complicated .. It is always recommended to keep localized DB separate.
For consolidation you can create another DB and consolidate the values
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,151
Super User 2024 Season 2
#2
Martin Dráb
229,993
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (