web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / Navision Upgrade, Merg...
Microsoft Dynamics NAV (Archived)

Navision Upgrade, Merger of Database

(0) ShareShare
ReportReport
Posted on by Community Member

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

I have the same question (0)
  • Suggested answer
    Amol Salvi Profile Picture
    Amol Salvi 18,698 on at

    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

  • Rashed Profile Picture
    Rashed 3,765 on at

    I suggest to do consolidation instead. You can run your reports based on consolidated company

  • ManishS Profile Picture
    ManishS 86 on at

    Merging multiple localization in one database is not recommended casue it will take a lot more effort and its very time consuming.

    Do as other member suggest.

  • Suggested answer
    4BzSoftware Profile Picture
    4BzSoftware 6,073 on at

    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.

  • Suggested answer
    Roberto Stefanetti Profile Picture
    Roberto Stefanetti 12,998 on at

    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans