R10 certain payments have PaymentMethodName null
Posted: Tue Dec 08, 2015 2:21 am
I noticed an unusual data issue this morning with one of our large clients.
Many of the store payment profiles records in ac_GatewayPaymentProfiles have a PaymentMethodName value that is null. I believe this is causing the PaymentMethodName on the ac_Payments record to be null as well.
This seems like a bug to me. If a stored profile was used to create the payment, there should be no reason for PaymentMethodName to be null. Unless maybe the field itself was added in a later release, and payment profiles created prior to that did not have a value.
But it's not all of them. Seems like it's about 50/50 - some have it populated, and some do not.
So looking at ac_Payments, about half of the payments have PaymentMethodName = null. So there's no way to tell if the payment was a Visa, MC, Discover etc.
Any thoughts?
Many of the store payment profiles records in ac_GatewayPaymentProfiles have a PaymentMethodName value that is null. I believe this is causing the PaymentMethodName on the ac_Payments record to be null as well.
This seems like a bug to me. If a stored profile was used to create the payment, there should be no reason for PaymentMethodName to be null. Unless maybe the field itself was added in a later release, and payment profiles created prior to that did not have a value.
But it's not all of them. Seems like it's about 50/50 - some have it populated, and some do not.
So looking at ac_Payments, about half of the payments have PaymentMethodName = null. So there's no way to tell if the payment was a Visa, MC, Discover etc.
Any thoughts?