BPSNAM: key too long 505(500) error appears when trying to save a new field in BPSUPPLIER table

Question

Hi, 
 Please I was trying to add a new field to a table when trying to save it pops up this error..please help me 
 Thank you 
 .

Rafael · Accepted Answer

Hello, 
 
 See the following KB:

Error: "Key too long xxx(500)"

Products

Sage X3

Country

North America

Description

Getting error when going into Table dictionary: "Key too long xxx(500)" 
 Example: Key too long 550(500)

Cause

The data type's Length was changed. 
 For example, in a confirmed case, in Table dictionary, a customer modified the ITM type on the ITMREF column. In the ITM data type, the Length was increased from 20 to 80. This caused the 500 byte max index to surpass the limit, to 550, thus generating the error.

Resolution

This requires knowing what was changed to cause this issue in the first place. If you do not know, you will need to use a stock system that's not been modified to compare. Once you've identified the problem data type and table, do the following: 
 
 In Table dictionary , select the table in question and go to the Index tab. 
 Make a note of the Index descriptor . Usually the Index code will show up in various error messages, showing the index that's the problem. 
 Go into the Columns tab and go into the Type for the column that's been changed and undo the changes to the Length field. You may decrease this number gradually (saving and validating the table) until the error disappears. 
 Save and Validate the data type and the table.

Sage X3

BPSNAM: key too long 505(500) error appears when trying to save a new field in BPSUPPLIER table

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING