TOPIC: Email template booking id not same as in booking

Hi,

I've got a question and this might be a bug.

When you open your own booking of an event, there is a Booking ID like 9D94CE1742.
But when I export a CSV file of this same event and I include the MAT_BOOKING_NUMBER variable, this shows another ID (like 9195F873D1).

I've tried some other variables in the CSV template but this doesn't give a solution:
- The MAT_BOOKING_ID variable shows the database ID of the person who made the booking (like 2140) in the CSV.
- The MAT_BOOKING_SID variable shows the database ID of the booking it self (like 3210) in the CSV.

How can I get the same booking id on the CSV export AND the booking screen in the front end?

This is important for us because we want to use this unique booking id as a SEPA mandate ID for Direct Debit payments. Therefor the booking ID the participant can see in his own booking must be the same that is on our CSV payment lists.

Thanks in advance for your reaction.

Hi Rob,

this bug has been fixed in Matukio 3.0.6 - it should have shown the correct id (which is shown under bookings) since then.

Best regards

Yves

Hi Yves,

Man, you are quick!
I just came to the same conclusion!
I saw I didn't have the latest release and just installed it and checked the CSV. And now it's OK.
I wanted to report this and retract my bugreport, but you already responded.

Cudos for your quick service!
Thanks

Hi Yves,

Sorry to come back to you on this subject, but I've got the same problem now with thee MAT_BOOKING_NUMBER variable when I use it in the email templates.
Specifically in the Booking Mail.
I'm on the latest version now (3.0.8 ).

I really need this to send a correct email to confirm the reservation and the SEPA mandate number (which the Booking number is for us).

Thanks
Rob

Hi Rob,

hmm wired, are you using the new or old booking form?

Best regards,

Yves

Hi Yves,

Again, a super fast response!
I should have mentioned it, but I'm using the old booking form.

Hi Yves,

Did you fix this?
The variable MAT_BOOKING_NUMBER now seems to give the correct value.

Hi Rob,

hmm yep i think so, should be fixed for a long time now.

Yves