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 -
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
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
Comments
Post a Comment