Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Master Data Upload Error - NAV 13
raghavasvrs
Member Posts: 2
Hi,
Please anyone suggest me a solution for this problem. While uploading master data to Navision 2013 I am getting an error stating "The Config. Package Table does not exist. Identification fields and values: Package Code='1', Table ID='15'".
However, my package id and worksheet is included with this table still I am getting the error. Please any one help me.
Raghav
Please anyone suggest me a solution for this problem. While uploading master data to Navision 2013 I am getting an error stating "The Config. Package Table does not exist. Identification fields and values: Package Code='1', Table ID='15'".
However, my package id and worksheet is included with this table still I am getting the error. Please any one help me.
Raghav
0
Comments
I have found that the error is due to the Package Code in the Spread Sheet not matching the Package Code in the database.
When NAV exports the template spread sheet it puts the Package Code and the table ID number at the top above the blue column headings.
What had happened was that the end user/customer had changed the Package Code. My client has two companies but requires only one Package, however as the Package was named after "Company X", when they provided the sheets for "Company Y" then changed all the references as they thought this differentiated the companies and changed it on every sheet.
Changing this reference in the spread sheet back to the correct Package Code resolved the issue.
Lead Consultant
Theta