Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 263 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Wave 2 Upgrade from BC Spring - Obsolete tables
martinjordt
Member Posts: 18
Hi all
Same as Ahmed described in an other post, I'm trying to upgrade a BC14 Cronus database to BC15.
https://forum.mibuso.com/discussion/comment/329584#Comment_329584
I'm faced with a slightly different problem than him though. In my case I'm upgrading from BC14 CU6 to BC15 CU4
I have followed the upgrade guide all the way to Task 8, Step 4 - Synchronizing with the Base Application extension.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-unmodified-application#task-8-synchronize-the-tenant
What I didn't think of, was that I should have verified that I didn't have any obsolete tables in my database - before I started the upgrade process. I forgot this because the guide didn't mention anything about this I guess.
Anyway - Now the Sync-NAVApp command stops with the error so many have already described: Unsupported table change; Change:Remove. And the synchronisation fails.
In my case the problem is with the old tables in the 700 range which would be the 'BA Db" objects, but it could be any obsolete table.
In Ahmed's topic he describes that came around his problems by simply deleting the tables, but for me that doesn't seem to be enough. I've deleted all the tables thru SQL directly, and yes I've deleted the tables for all the companies, but I still get the same error.
Have anyone here found a way around the problem regarding obsolete tables in the database - other than to restore your backup, and start all over again
Regards
Martin
Same as Ahmed described in an other post, I'm trying to upgrade a BC14 Cronus database to BC15.
https://forum.mibuso.com/discussion/comment/329584#Comment_329584
I'm faced with a slightly different problem than him though. In my case I'm upgrading from BC14 CU6 to BC15 CU4
I have followed the upgrade guide all the way to Task 8, Step 4 - Synchronizing with the Base Application extension.
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-unmodified-application#task-8-synchronize-the-tenant
What I didn't think of, was that I should have verified that I didn't have any obsolete tables in my database - before I started the upgrade process. I forgot this because the guide didn't mention anything about this I guess.
Anyway - Now the Sync-NAVApp command stops with the error so many have already described: Unsupported table change; Change:Remove. And the synchronisation fails.
In my case the problem is with the old tables in the 700 range which would be the 'BA Db" objects, but it could be any obsolete table.
In Ahmed's topic he describes that came around his problems by simply deleting the tables, but for me that doesn't seem to be enough. I've deleted all the tables thru SQL directly, and yes I've deleted the tables for all the companies, but I still get the same error.
Have anyone here found a way around the problem regarding obsolete tables in the database - other than to restore your backup, and start all over again
Regards
Martin
0
Comments
I have done a converting to BC15 CU4 a couple of days a ago.
I had a similarly problem, my problem was that a table was present with a ID in the Microsoft range and that table was not in the new Base application, my solution was to go back to BC14CU1 and delete the table in C/Side with force, and after that I could run the upgrade without any errors.
Perhaps this can help you
Yes I could do that, but I would like to reserve that as a last resort. I know right now it's just a Cronus database, but I would rather like to know if there is a possibility to salvage the operation without starting all over for the day I'm upgrading a mother of a customer solution