Every list showed the wrong account owner

A customer, lead, deal or task created in the app showed Unassigned in every list, however plainly it had an owner on its own record page.

A record that arrived with your sample data did the opposite: it kept naming whoever it started with. You could change the account owner, see the change save, reopen the list, and read the old name. Changing it again changed nothing. It was not a screen that needed refreshing; it would have named the wrong person for good.

The cause is the same in both cases. Who owns a record is a field on the record, and it is what a save writes and what permissions read. The lists were reading a separate table of people attached to a record, one that nothing in the product has ever written an owner into.

Creating a vendor without typing a code of your own failed with a server error. So did recording a payment: one made to a vendor, or one received from a customer. Each of the three asks “is this number already used?”, and that question was being put to the wrong table.

These were not rare edge cases: leaving the code blank is the ordinary way to create a vendor, and there is only one way to record a payment.