The Fields in an active key may not exceed 252 bytes.

upasanisandip
Member Posts: 405
Hi,
I am importing data through Dataport. In Item table(Table 27) NO. Field is of length of 20 but I want to increase that upto 50.
But getting message that
"The Fields in an active key may not exceed 252 bytes.
The size of the Search Description , No. key fields in the Item table is 280 byes.
You must reduce the number or length of the active fields."
What could be the solution for this ..
Any hints or suggessitions.
Thanks,
Sandip.
I am importing data through Dataport. In Item table(Table 27) NO. Field is of length of 20 but I want to increase that upto 50.
But getting message that
"The Fields in an active key may not exceed 252 bytes.
The size of the Search Description , No. key fields in the Item table is 280 byes.
You must reduce the number or length of the active fields."
What could be the solution for this ..
Any hints or suggessitions.
Thanks,
Sandip.
0
Comments
-
0
-
First and for all:don't do it! But create an extra field for it.
But I will give some info about the error.
It means that a key may NEVER be larger then 252 bytes.
Each secondary key includes the keyfields of the primary key that are not yet in the secondary key.
So you have a big key and Navision adds "No." to it and so this key goes over the limit of 252 bytes.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
upasanisandip wrote:Item table(Table 27) NO. Field is of length of 20 but I want to increase that upto 50.
Imagine the order entry :twisted: HELL :twisted: of having to enter this many characters for every order.
I'm from the belief that there are many places to describe an item in Navision. The Item No is not one of them. We tried that years ago in our last system but eventually it goes off track.
We keep it simple 5 characters allows us at least 00001..99999 items and thats if we don't even use letters.
Then we can use the Maxlength & Next controls very efficiently to automatically pop to the next field once it's been filled. We have 100's of lines on every order so saving as many keystrokes as possible is a winning proposition.
and order entry doesn't get carpal tunnel0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions