Customer Change Mystery

We have 4 or 5 customer records in which 9 checkboxes have mysteriously changed from true to false, rendering the customer mostly unusable until they are reset.
the fields are:
Customer.ValidPayer
Customer.ValidSoldTo
Customer.ValidShipTo
Customer.AllowOTS
Customer.PrintAck
Customer.PrintLabels
Customer.GlobalCreditIncOrd
Customer.OneInvPerPS
Customer.FinCharges
They show in the Change Log. The user shown in Change Log has not unchecked the boxes, They would have had to make the changes on three separate tabs of the customer within 10 seconds, and that does not seem likely, and they insist that they do not ever change all those checkboxes.

So, what could cause these fields to change?
I have looked through all our BPMs and found nothing that touches these fields.
We have Avatax and CertCapture (now ECM), and a few times these changes seemed to be around the time of a new certificate input into CertCapture and an old one deleted.
We also have customizations from Century Business (eBizCharge) for credit card processing, I’m going to send them this question too.
Is there some function or feature baked into base Epicor that might cause this to happen?

Did you ever solve this???

I just discovered the exact same thing happening in our environment… makes zero sense; we even make all those fields read-only via extended properties maintenance so users can’t change them through the UI.

We also have Avalara and CBS.

Have you tried using the inactive field in the Kinetic UI? That field does not exist in Classic UI, and maybe marking a Customer inactive changes all of the other flags. :man_shrugging:

I’ll check that out. The most bizarre part is that one of the fields getting changed is a UD field.

It wasn’t this… haven’t been stumped this badly in a long time…

I never got a resolution to this mystery. Epicor Support checked with Avalara Support, and both said their software would not change those values. Without reproducing it, they couldn’t troubleshoot any further.
It did recur once in our db for the same 3 or 4 customers about a month or two after the initial discovery. But, again I couldn’t trace it to anything in particular. It has not recurred again.

1 Like

@alintz , I ended up creating a data directive to throw an error and prevent the fields from actually changing.

I’ve had 2 users report the error message since then, but all I’ve learned from that is it likely has something to do with pulling in multiple customers into Customer Maintenance and switching from one to another. Maybe some weird permutation of the nav bar arrows and the Save, Refresh, and Clear buttons (possibly interacting with some quirk in the datasets of the customers pulled into Customer Maintenance), but I still cannot recreate it on demand.

I still hope to get to the bottom of this but at least for now the data directive is stopping all the chaos that had been ensuing from corrupted data.

1 Like

Good idea on the BPM. I may implement that also. I have not had a recurrence in months (that I know about).

1 Like