Has anyone had any custom programing done to allow for sales orders to have alphanumeric and special characters? Just wondering if it is even possible?
Not possible.
I assume someone wants to build a “smart” order number. Good database practice tells us not to put multiple items into one column/field, i.e. First Normal Form.
Still a large job, but possible is to add UD field(s) to the OrderHed. Next you would then add that field everywhere you wanted it to display.
Are you sure there isn’t another way to accomplish the unstated business goal?
We are creating orders in Epicor from an outside source, Shopify. Our order number sequence in Epicor started at 10,000 and our Shopify order sequence started a 1000, so at some point we will get to 10,000 in Shopify and orders from Shopify will no longer be able to be made in Epicor because of duplication. Since it is not possible I will look into changing the numbering sequence in Shopify to avoid order number duplication. Thanks for your input.
Ahhhh, I see.
Another option is to create a new UD field in OrderHed and place the Shopify order number there and now you have a cross-reference between the two and never have to worry about collisions. You can even make the Shopify Order Number a link that sends you to the order from Epicor. It can also be displayed in emails, forms, etc.
Good suggestion, I’m already placing that number in a UD field on the order header so it would be fairly easy to make the switch.
1 Like
Seconding @Mark_Wonsil and to expand upon it, I’ll add my own general rule. Always avoid using the same ID as a customer/outside platform as your internal key. Don’t use their SO, Part#, anything if possible. If you do, you’re stuck ingesting whatever bad practices (or even just practices tailored to their systems) your partner elects to pursue.
1 Like