Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K 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
- 280 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
Upgrade to NAV2013R2 messages at step 9b
mdPartnerNL
Member Posts: 802
While updating with this document http://blogs.msdn.com/b/nav/archive/201 ... 13-r2.aspx
in step 9b you need to import all new 2013R2 objects.fob.
Below are some of the messages I got and below it I added the solution to solve it. Hope it helps someone else.
The Description field with 11 ID in the Sales Invoice Line table has been deleted
from metadata, but the table contains data in the ... database.
Table: 113
Solution: The length of Field 11 was set to 250 in 2009 by the partner, but in NAV2013R2 the length is 50
The field Aantal with ID 50020 in the table Sales Cr.Memo Line cannot be deleted
or changed because the field contains data in the ... database of the ... company.
Table: 115
Solution: Field 50020 didn't exist in the new prepared 2013R2 code (mistake)
The field Update BizTalk Partner Setup with ID 80 in the table VAT Rate Change Setup cannot be deleted
or changed because the field contains data in the .... database of the ... company.
Table: 550
Solution: Field 80 didn't exist in the new prepared 2013R2 code.
But this table doesn't exist in the original NAV2009R2 Base database too..? So was a new field in NAV2013??
The Description field with 12 ID in the To-do table has been deleted from metadata,
but the table contains data in the ... database.
Table: 5080
Solution: The length of Field 12 was set to 75 in 2009 by the partner, but in NAV2013R2 the length is 50
The operation could not complete because a record in the Access Control table was locked by another user. Please retry the activity.
Solution: Compile some other objects first (disregard the errors), then do the import of 100 objects. In batches it will work.
in step 9b you need to import all new 2013R2 objects.fob.
Below are some of the messages I got and below it I added the solution to solve it. Hope it helps someone else.
The Description field with 11 ID in the Sales Invoice Line table has been deleted
from metadata, but the table contains data in the ... database.
Table: 113
Solution: The length of Field 11 was set to 250 in 2009 by the partner, but in NAV2013R2 the length is 50
The field Aantal with ID 50020 in the table Sales Cr.Memo Line cannot be deleted
or changed because the field contains data in the ... database of the ... company.
Table: 115
Solution: Field 50020 didn't exist in the new prepared 2013R2 code (mistake)
The field Update BizTalk Partner Setup with ID 80 in the table VAT Rate Change Setup cannot be deleted
or changed because the field contains data in the .... database of the ... company.
Table: 550
Solution: Field 80 didn't exist in the new prepared 2013R2 code.
But this table doesn't exist in the original NAV2009R2 Base database too..? So was a new field in NAV2013??
The Description field with 12 ID in the To-do table has been deleted from metadata,
but the table contains data in the ... database.
Table: 5080
Solution: The length of Field 12 was set to 75 in 2009 by the partner, but in NAV2013R2 the length is 50
The operation could not complete because a record in the Access Control table was locked by another user. Please retry the activity.
Solution: Compile some other objects first (disregard the errors), then do the import of 100 objects. In batches it will work.
0