|
saada
|
October 10, 2014 at 2:48 pm
Hello,
We are finding that in the EE 3.1.36.5.P, the “Amount Paid” column is incorrect when there are multiple ticket types purchased.
For example, someone who buys 3 tickets for a total of $40 on the same transaction, there are 3 rows for the 3 tickets. The “Price” column is correct in listing these prices; however, only the first row for “Amount Paid” column shows an amount, which happens to be the total sales price (the others show $0).
For reference, this is how it looks for a single transaction where there are 3 tickets purchases (the last row being a free child/$0 ticket):
Transaction ID Price Attendees Amount Paid
xxxxx123 24 3 40
xxxxx123 16 2 0
xxxxx123 0 1 0
Shouldn’t this display the amount paid for each ticket instead so we can filter how many tickets were sold for each type and their respective amounts?
Transaction ID Price Attendees Amount Paid
xxxxx123 24 3 24
xxxxx123 16 2 16
xxxxx123 0 1 0
If the transaction was incomplete or declined, I would think it would show:
Transaction ID Price Attendees Amount Paid
xxxxx123 24 3 0
xxxxx123 16 2 0
xxxxx123 0 0 0
Am I missing something? We sell thousands of tickets so I really hope we won’t have to manually reconcile this later. Please advise.
|
|
Josh
|
October 13, 2014 at 11:04 am
Hi there,
It turns out what you’ve reported here is from a limitation in Event Espresso 3’s event price database table structure. This structure was completely rewritten for Event Espresso 4 so the tickets unlike the way ee3 worked.
For example, in 3.1 each row in the event_attendee table corresponds to an attendee who may have multiple tickets/registrations for an event. This was rewritten for EE4 so every single row in the registration table relates to a ticket for somebody to get into the event.
|
