Error on adding row to dropdown editor - not alphanumeric

[stevec]

Hi,

Up until a recent upgrade to 6.2 from 5.1, we have a large number of entries in a dropdown list that contain '-' characters in the item name (not the value). In fact, it's a guid like the sugar record ids.

Now, when trying to add such a new row, we get the error message:

"Key - Must be alphanumeric, begin with a letter and contain no spaces."

To get around this, I'm having to modify the custom language file directly on the server to add new rows.

I've looked at the codebase to see where this error is generated (the text is represented by the 'LBL_JS_VALIDATE_KEY' label - but being javascript it's very difficult (for me) to see what I need to change.

Can anyone point me in the right direction?

Thanks

[Angel]

You really shouldn't modify the language file to circumvent this matter. The reason why the interface does not allow you to use spaces and the like is because its been known to cause problems when editing the list, more specifically, saving values.

This was a major pain if it happened to you after having entered 20, 30 values, as none of the values would be saved.

I am not sure what other problems it can cause, but I would assume that if they don't allow certain characters, there are likely other problems they intend to prevent.

[stevec]

Thanks - but it's something we cannot avoid at the present. Do to the legacy integrations, we need the guids values in the dropdown items.

The editing works in this circumstance - and once in there, the dropdowns can be edited and moved.

[martyp]

Thanks - but it's something we cannot avoid at the present. Do to the legacy integrations, we need the guids values in the dropdown items.

The editing works in this circumstance - and once in there, the dropdowns can be edited and moved.

Did you ever find a way to over ride the error? I've noticed that a number of the DEFAULT entries within Sugar 6.4.4 have spaces in the item name, have a look at the lead_source_dom drop down list (Studio > Contacts > Fields > lead_source) You'll see a number of entries have item name listings that have spaces in them, however, when you try to create one with a space, you get the following error:

Key - Must be alphanumeric, begin with a letter and contain no spaces.

Surely this is a bug? An edit to the JS that is doing the checking should fix it, does anyone have any ideas on where/what JS is used to check the drop down item name entry?