Skip to main content


Showing posts with the label Upgrade

Remove unsupported characters with Sanitizing Your #msdyn365bc Data.

Hi Readers, With start of New Year, I saw a new issue and learned something with that. This reminded about an old article that I have written in past during data upgrade from Classic to RTC Version. While writing that I thought this will never come up again but to my surprise that it's still there, but this time story is little bit different. This time Microsoft added a process to fix these data issues.

Q & A From - Preparing your BC upgrade – A panel discussion.

Hi Readers,      I am so grateful to be co-presenting with leaders in the community.  For my little experience of 10 years with Dynamics NAV and Business Central, I always referred to their Books and Blog Posts. I was super excited to be a part of Panel Discussion with Luc van Vugt & Jon Long . Thank you for @Reports_ForNAV , @areopanl , @lucvanvugt & @jonwlong for planning, scheduling, and helping during the webinar.

MSDYN365BC - Upgrade to Business Central Now.

Hi Readers, Hope you are doing good and staying healthy and safe during this Pandemic. Today I wanted to discuss and share about Licensing for Business Central and how it effect your upgrade decision. ** All the information shared in this article is based on what is current available from Microsoft and my analysis of that information. Please reach out to your partners for confirmation. ** I am not an licensing expert. If you have questions after this article, please read till end. A Webinar is schedule for Licensing Q&A. 

The metadata object Table was not found - Error during Data Upgrade To NAV 2013, NAV 2013R2 & NAV 2015.

Hi Readers, In Archerpoint we would like everyone using NAV / Business Central in the community to be Stay Current , which means stay on the latest and greatest version of the product. We are upgrading one of the customers to the latest and greatest version to Business Central 2019 Wave 2 from NAV 2009 with multiple companies. This article applies if you are Upgrading to #NAV2013, #NAV2013R2 & #NAV2015. Everything was working fine till we started data upgrade to NAV 2015 from NAV 2009. During Data Upgrade to NAV 2015 system generated error message.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

MSDYN365BC - Upgrade To Microsoft Dynamics 365 Business Central on premises - No of Steps?

Hi Readers, As Microsoft Dynamics 365 Business Central on-prem released, I am getting questions about how many steps do we need to upgrade (Data migration & Object Merge) to MSDYN365BC (on-Prem). This article just lists down No. of steps required to upgrade From Current Version 3.7 onward.

Data Upgrade to Microsoft Dynamics NAV 2018.

Hi Readers, In this article, we will discuss data upgrade to NAV 2018 from NAV 2017 (Cronus Database). Steps will remain same for the NAV Version 2015 and 2016. Data Upgrade to NAV 2018 in one step is from - 1. NAV 2013.      * 2. NAV 2013 R2. * 3. NAV 2015. 4. NAV 2016. 5. NAV 2017. * Read at the End of article.

Upgrade From Classic To RTC - Issue with Line Feed and Horizontal Tab (Version 3.0)

Hi All, Today I would like to discuss an Update on a Old Article which discuss the resolution for issue that we have during upgrade from Navision Classic Client to Navision RTC Client. Old Article Reference   What is the issue ?  The Issue is with the data having Line Feed & Horizontal Tab. On Which Fields the issue is? The major issue is with the Primary key field. On Fields other than primary key it doesn't make much of the difference.

Upgrade - Database Archive for Microsoft Dynamics NAV.

Hi All, Now a Days as most of the work that partners have is upgrade. It would not be wrong to say that even Microsoft have discontinued Support for Microsoft Dynamics NAV 2009 and Previous version, we still have so many customers who are actually using them. There are some customer still using version 3.7 or 2.0 but majority of customers are either on 4, 5 and 2009. Now when we as Microsoft Dynamics Partners plan to upgrade a customer to NAV 2013 / NAV 2013 R2 / NAV 2015 and NAV 2016, first thing that we look for is the Microsoft Database (objects) of the base Version which is currently the Customer Version. Where we can find the databases for these Old Versions of Microsoft Dynamics NAV? 

Upgrade To NAV 2013 or Later - Transferring Record Links From 5.0 or 2009 To 2013 or Later.

Hi All, Today we will discuss an Common Issue which we face during upgrade to NAV 2013 and Later from NAV 2009 or Previous Versions. After Data Migration All Data come as-is but Due to some Reason the Migration Process did not process Record Links To New Version. The Table 2000000068 Record Link Which we are discussing in This Article, have different architecture in NAV 5.0, 2009 and 2013 Onwards. That Might be one reason. All Thanks To  +Suman Maharjan  , For Raising the Issue To me.

Upgrade From Classic To RTC - Issue with Line Feed and Horizontal Tab.

Hi All, Today I would like to discuss a issue that we have during upgrade from Navision Classic Client to Navision RTC Client. What is the issue ? The Issue is with the data having Line Feed & Horizontal Tab. On Which Fields the issue is? The major issue is with the Primary key field. On Fields other than primary key it dosent make much of the difference.

Best Practices For Upgrade From NAV 2009 R2 to NAV 2015 Released From Microsoft.

Hi all, In Last Week, Microsoft have released Best Practices Steps that we should follow during Upgrading a Database. The Best Practices List the Steps while Upgrading a Database - From NAV 2009 R2 to NAV 2015. From NAV 2013 to NAV 2015. From NAV 2013 R2 To NAV 2015. Even if you are upgrading From NAV 2009 R2 to NAV 2013 / NAV 2013 R2 do read the Best Practices. The Article contain the points that we need to take care during Migration.

Key Pointers During Data Migration to NAV 2013 R2.

Hi All, As we all know that there is Document Shipped with every product DVD of Navision which list down the steps for Data Migration. In some new version it was not shipped in product and was released later in Microsoft Team Blog. What we do is we follow the steps listed in the Document and do the data migration, but in certain cases we face issues for which we don't have any reference in the document shipped from Microsoft. The Reason of Issues can be data related, Hardware Related & Service Related. In this article i will try to add some of my findings during data migration and will keep of adding points in future whenever i stuck with issues. This article will act as checklist for data migration to NAV 2013 R2. #Saurav - Added on 07-04-2015

Data Migration To NAV 2013 R2 - Error in Step 2.

Hi All, It's been a while that i haven't blogged anything. Today i would like to discuss an issue raised to me by most of the Readers that they face during Data Migration in Upgrade Activity. The Error message occurs before step two after opening database in NAV 2013 R2. When we open our database in NAV 2013 R2 and import customized objects and then try to Run the NAV 2013 R2 Client, it behaves in an unexpected manner . Instead of opening the client it says - The operation could not complete because a record in the <<>> table was locked by another user. Please retry the activity. OR A connection to the server has been established. preparing your work space. OR Fields cannot be found in Marketing setup..

Data Migration Steps From NAV 2013 to NAV 2013 R2.

Hi All, This was asked to me from so many readers about the steps that we need to take for data migration from NAV 2013 to NAV 2013 R2. Yes those steps are listed in MSDN but at the same time they are so much confusing as they have merged the steps of both Data Migration as listed below- 1. NAV 2009 / SP1 / R2 TO NAV 2013 R2. 2. NAV 2013 TO NAV 2013 R2. So for those who are looking for steps that need to be executed to upgrade data from NAV 2013 to NAV 2013 R2, do read the post.

How To - Restore Native Backup to SQL Database. (SQL Migration)

Hi All, In this post we will be discussing how we can move a Native Database to SQL Database. In Simple Words If a customer is Using Native Database (FDB), how we can move that database to SQL Server. So if you know how to do SQL Migration rest is something you will not be interested in. Others who want to learn it please read the complete article.

Upgrade NAV 2013 / R2 Error - System.Int32.get_HasRows failed with this message.

Hi All, During a Upgrade Project from NAV 2009 SP1 to NAV 2013. Step 1 was performed successfully. But After Converting Database to NAV 2013 and Running Upgrade Step 2 I found an error message. Below is the Screen Shot of the Error Message -

Upgrade Error - The database collation cannot be changed if a schema-bound object depends on it.

Hi all, Found a issue while upgrading from Navision 5 SP1 to NAV 2013 related to database collation. Posted the issue on mibuso and got the hint to resolve same. I thought I should share it with you all, so here it is.

How to Import Text File In Developer Toolkit?

Hi all, In Previous post we had seen  A) How to install Navision developer Toolkit   B) How to create developer toolkit databases. Let's see how to import database objects into toolkit database.

How to Create Navision Developer Toolkit Database?

Hi all, In previous post we had seen how to install developer toolkit . Now for performing any action in developer toolkit we require a developer toolkit database.