Epicor version 9.05.701 Is there an official list of what characters NOT TO use in the part.partnum field? I’ve read its recommended to stay with alpha-numeric but wondered what specific characters to definitely avoid and what impact it could have if used. Thanks in advance.

Thank you for the responses. I was just curious if there is anything official documented about this. I’ve emailed epicor support too and awaiting their response.

There are multiple things at play here… keeping in mind that the Part.PartNum field is a TEXT field, it can physically accept any text character. Including an asterisk. And yes, I’ve had customer who used BOTH asterisks and question marks in their part numbering scheme. BEST PRACTICE is an entirely…

We had so many issues that we had to create a Data directive on part table with this condition code which if true, is generating an exception message to the user, preventing the save. “If new added row, and the condition of the personilized code is valid:” foreach(var part in ttPart) { if(!new Sy…

[image] Hogardy: if(!new System.Text.RegularExpressions.Regex("^[a-zA-Z0-9_-]*$").IsMatch(part.PartNum)) Just one small adjustment… if(!new System.Text.RegularExpressions.Regex("^[A-Z0-9_-]*$").IsMatch(part.PartNum)) There, that’s better. :wink:

Epicor consulting did create an “Epicor Part Numbering Standards.pdf” doc with this section from it: [image] EDIT: shout out to @timshuwy who put it together :slight_smile:

Em dashes, quotes, and fancy quotes kill us. An Em dash (the fancy longer dash) worked its way in, and we ended up with 2 p/n’s that looked the same, but only the one with the regular dash could be entered from the keyboard. Quotes and apostrophes can causes issues when exporting. People used the…

Clipped off a very important part of that page … [Screenshot_20180622-174420]

we send out a data fix that removes leading spaces on a not infrequent basis because " partnumhere" and “partnumhere” look the same in the UI, but, are really two different things. Please, avoid spaces in the part number field!

Thank you for all the replies on this. This is most useful. To go “full circle” on this, we were using costing workbench, loading parts but not all were appearing in the purchased / manufactured tabs.

Part.PartNum field special characters

Epicor ERP 9

timshuwy (Tim Shoemaker) June 22, 2018, 8:48pm 9

Attached is the complete document on Part Numbering Standards… it was written in 2013, but nothing has changed. It explains all the reasoning:
Part-Numbering-Standards-WP-ENS-0614.pdf (1.0 MB)

Dear Epicor, it's time to abandon leading spaces as valid characters

Topic		Replies	Views
Illegal Characters In Part Numbers - anyone have a list of them? Epicor ERP 10 e10	6	2464	November 10, 2020
Symbols in Part Numbers Yahoo Archive	1	740	September 17, 2015
Part Number Epicor ERP 10 e10 , epicor	10	947	July 17, 2020
PartNum trailing spaces Epicor ERP 10	12	2338	February 9, 2023
Non-ASCII and Trailing whitespace on key fields (like PartNumber) Epicor ERP 10	6	1308	October 26, 2016

Part.PartNum field special characters

Related topics