Any issues with making a field unique? Customer.CustID

We need to keep the CustID unique in our system as the legacy data doesn’t have a Company designation to keep them separate.

I’d like to just throw a constraint on the database but don’t want to mess with anything I shouldn’t be.

Is there a better way to do this?

CustID is unique in the Customer table.

Or were you refering to its use in other tables?

Unique across all companies is what I need. Currently have CustID of 17441 in Company ‘200’ and ‘250’

Need to make sure it doesn’t happen again.

Thanks

Okay … missed that part about Company field.

You could make a BPM that would prevent creating a CustID if it already exists in the Customer table - regardless of the Company field.

But what is your plan when legacy data to be imported contains a CustID that is already in use?

No clue but there are only 2 of those.

I figure I’ll need to talk to the finance person and see if there’s a way we could remove the order, enter a new one under the new CustID and run that order through.

I’d REALLY prefer to just change the CustID (correction: CustId is not on OrderHed) on the OrderHed table, but I’m concerned that I’ll break something. Although, come to think of it, Epicor uses CustNum throughout the system so maybe if I just updated the CustID on that record it would meet my needs?

Thoughts?

You are in luck!!! The whole system bases ebverything on the CustNum. The CustID is like an alias for the CustNum. You can change the CustID whenever you want.

Just load the Customer in Customer Maintenance, then click teh Change ID button

image

Awesome! Thanks for the support Calvin!

Worked like a dream, I just had to build a script to fix up the legacy data as well.

You still need to implement a BPM to prevent using a CustID of an existing customer from a different company. (I assume, in the future, you’ll make new customers through the UI)