Skip to main content

Data Upgrade to MSDYN365BC 2019 Wave2 Error - Field:DIOT-Type of Operation; Change:Remove.

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.

Everything was working fine till we started data upgrade to Business Central 2019 Wave 2.


During Sync Base App from Microsoft to Business Central, System generated the following error message.

Sync-NAVApp : 
Table Vendor :: Unsupported field change. Field:DIOT-Type of Operation; Change:Remove
Table Purchase Header :: Unsupported field change. Field:DIOT-Type of Operation; Change:Remove
Table Gen. Journal Line :: Unsupported field change. Field:DIOT-Type of Operation; Change:Remove
Table Purch. Inv. Header :: Unsupported field change. Field:DIOT-Type of Operation; Change:Remove
Table VAT Entry :: Unsupported field change. Field:DIOT-Type of Operation; Change:Remove
Table Purchases & Payables Setup :: Unsupported field change. Field:DIOT Default Vendor Type; Change:Remove
Table VAT Posting Setup :: Unsupported field change. Field:DIOT-WHT %; Change:Remove


 So what could possibly be wrong in this case?

Thoughts When upgrade generated these errors?

 1. We might have not removed some Custom fields named -

  • DIOT-Type.
  • DIOT-Type of Operation.
  • DIOT Default Vendor Type.
  • DIOT-WHT %

Checked back in the Business Central 14 database. No Custom Fields Found.

 After analysis, we found out that team did not follow what Microsoft suggests upgrading to Business Central 2019 Wave 2 (15.x) from Business Central Spring Release (14.x).

So what team Missed - 

When upgrading to Business Central 2019 Wave 2, we need to make sure that we are in a specific Cumulative Update for Business Central Spring Release (14.x).

If you are upgrading to Business Central 2019 Wave 2, Keep these in Minds -

Upgrade To - Microsoft Dynamics 365 Business Central 2019 Wave 2 (CU 0).
From            - Microsoft Dynamics 365 Business Central April'19        (CU 04 & CU 05).

 Upgrade To - Microsoft Dynamics 365 Business Central 2019 Wave 2 (CU 01).
From            - Microsoft Dynamics 365 Business Central April'19        (CU 06).

 Upgrade To - Microsoft Dynamics 365 Business Central 2019 Wave 2 (CU 02).
From            - Microsoft Dynamics 365 Business Central April'19        (CU 07).

So what does that mean - You should always be on the latest version of Business Central 14.x to upgrade to latest version of Business Central 15.x.

If you are not on the latest cumulative update of Business Central 14 then choose your target version of Business Central 2019 Wave 2 which maps to that specific version for the upgrade.

Happy Upgrading.

Let me know your views on the article as a comment.

Regards,
Saurav Dhyani
www.sauravdhyani.com
Labels:
Location: House No. 1, Shivlok Colony 2, Near Himalayan Academy, Post Office, Shivlok Colony, Sewla Kalan, Majra, Dehradun, Uttarakhand 248171, India

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

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.
21 comments
Read Complete Article »

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.
Post a Comment
Read Complete Article »