Hey everyone,
Quick question.....does anyone know where customer_last_ticket_date pulls it's data from in output set elements? Is it supposed to be the last date a ticket was printed? I know where T_QUERY_ELEMENT is pointing in T_CUSTOMER to get this. But what doesn't make sense is where T_CUSTOMER is getting this date.
- Chris
I think it's the sale date. I just sold myself an unseated ticket and it updated T_CUSTOMER.last_ticket_dt.
The update appears to be coming from "called from TP_ORDER_SAVE_UPD as part of order save process"
I don't know that that is true. I just looked at an account that has a last ticket date of 10/19/18. No transactions for that account even took place on that date (meaning no order, contributions, or printed tix). Another account has the last ticket date as the last activity date. And another account has a last ticket date that doesn't match anything I can find with dates on the account. There are accounts where the last ticket date does match the last time a ticket was printed or an actual transaction happened. However...there is no rhyme or reason to any of it.