In our Magento database we have 40 records in our
customer_entity table that have an
entity_type_id that maps to an
entity_type_code of 'customer_payment' in the
eav_entity_type table. They are stopping us from converting to global account sharing between our stores. What are they for and can they safely be deleted?
We are preparing to launch our second store on Magento Enterprise Edition v22.214.171.124 and we have recently decided to turn on global customer account sharing before launching the new storefront. All that should be required for this is to ensure that there are no email address collisions between the two stores' accounts, so I deleted test accounts for the new storefront expecting that we would be set but that is not the case.
Upon inspection of the records in the
customer_entity table I found 40 records as described in the "short version" above. They are all created in quick succession of one another- just a handful of seconds to create them all- which leads me to believe that they must be auto-generated. Most fields are null or set to zero, including
I searched every table that had a foreign key reference to the
entity_id field of the
customer_entity table for occurrences of the offending ids but they do not appear to be related to any other records in any other tables, at least not to those that enforce a foreign key relationship. It appears that even if they were related by foreign key relationships the database schema would gracefully cascade deletes and set values to null as needed.
A Google search for Magento & customer_payment yields very few results and none of any real use. All I've been able to determine is that 'customer_payment' appears to be a default entity type for Magento. I even went as far as to do a fresh install to see if the customer records might be auto generated at install time, but that is not the case.
So why are these present? What purpose do they serve, what generated them, and most importantly can I safely delete them?