Using Special Characters in Elliott Item Numbers

Using Special Characters in Elliott Item Numbers

Release Date: 4/27/2021
Version: 7.5 & Higher

Q - Are there any special characters I should avoid when creating a new item number?  For example, which one of the following are preferred item numbers:
  • HCC451-30
  • HCC451_30  
  • HCC451/30
  • HCC451*30
  • HCC451 30
  • HCC451(30)
AHCC451-30 is the best choice. Any characters that have special interpretations by the file system are a bad choice to use for item numbers. If you want to use Elliott’s “link” feature for item image, spec, drawing files, then the item number will be part of the file name. Therefore, if your item number contains special characters that are not suitable to be used for a file name, the link feature for that item won’t work.

The “(“ or “)” symbols are OK to use, and so is the underscore "_". But they are not our first choice. The dash(hyphen) “-“ is commonly used in a file name, so it is our first choice. Spaces may be interpreted as a "terminators" in command lines and should be avoided.

In the above example, the forward slash “/” or back slash “\” are bad choices because they are used by the file system as separators. The EDI system uses asterisk "*" symbols extensively as separators.  

The following article has good a explanation on what characters should be avoided for file naming:

Do not use any of these common illegal characters/symbols:
  • # pound
  • % percent
  • & ampersand
  • { left curly bracket
  • } right curly bracket
  • \ back slash
  • < left angle bracket
  • > right angle bracket
  • * asterisk
  • ? question mark
  • / forward slash
  •   blank spaces
  • $ dollar sign
  • ! exclamation point
  • ' single quotes
  • " double quotes
  • : colon
  • @ at sign
  • + plus sign
  • ` backtick
  • | pipe
  • = equal sign
Also, keep these rules in mind.
  • Don’t start or end your item number with a period, hyphen, or underline.
  • Avoid using spaces; use a hyphen instead.

EMK

    • Related Articles

    • Special Character Not Allowed in Elliott Password

      Release Date: 04/26/2022 Version: 7.x & Above Q - Is there a list of special characters that we cannot use in the password field for user accounts? We are tweaking our password reset utility on our website and just want to make sure we align with ...
    • How to Use Notepad++ to See Special Characters In Your ASCII Import File

      Release Date: 07/10/2019 Version: All Q - When trying to import the attached file, there is an error on line 30. Error message :The 1st Byte must be H, N, L, T, O or I. When the file is checked it appears that the data on line 31 is out of alignment ...
    • Do Not Use Extended ASCII Characters

      Release Date: 2/15/2019 Q - I've run out of characters for Material Cost Types using what's available directly from the keyboard (numbers, letters, punctuation). Will Elliott properly recognize extended ASCII characters? For example: ALT+0188 gives ...
    • Receive 'Invalid Column Name' Message After Starting to Use Alphabetic Document Numbers

      Release Date: 4/5/2019 Version: 8.5 & Up Q - I just started to use alphabetic order numbers in Elliott 8.5, and my FedEx shipping manifest machine is giving me a message : The Following Errors Occured While Tring to Process a SQL Request SHIPPING ...
    • Can You Explain How Elliott Stores Serial Numbers in Its Database?

      Q - Can you explain the various Lot/Serial files (IMLSHST, IMLSTRXS, IMSERREF, etc) - how/when they are populated/updated by the Elliott application and how they relate to other files? A - Here is a highlight of each one of the Elliott database ...