Using illegal characters in id-ne fields

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Using illegal characters in id-ne fields

jonwimp
Is it absolutely wrong to use illegal characters in productId field?

What are the reasons not to use illegal characters in productId?

I encountered one: Javascript function names don't work with ' ' (spaces), so the QuickAddVariants
page is broken if you use ProductFeature(s) with Id(s) that contain spaces.

Am doing a data migration, so I encounter illegal characters.

Jonathon
Reply | Threaded
Open this post in threaded view
|

Re: Using illegal characters in id-ne fields

David E Jones

There are all sorts of problems with such characters. Most of them  
are related to web-related standards like HTTP (especially in URLs  
and URL parameters), and like you mentioned in JavaScript, and of  
course both of these are related to HTML.

It's generally a good practice anyway to use a pretty limited set of  
characters for IDs. You never know what you'll want to do in the  
future, like maybe print it as a barcode or something... and  
depending on the barcode standard you go with you'll have a varying  
set of characters available.

-David


On Jan 27, 2007, at 10:45 AM, Jonathon -- Improov wrote:

> Is it absolutely wrong to use illegal characters in productId field?
>
> What are the reasons not to use illegal characters in productId?
>
> I encountered one: Javascript function names don't work with '  
> ' (spaces), so the QuickAddVariants page is broken if you use  
> ProductFeature(s) with Id(s) that contain spaces.
>
> Am doing a data migration, so I encounter illegal characters.
>
> Jonathon


smime.p7s (3K) Download Attachment