The Order class has Email, FirstName & LastName properties although I'm not sure what they are used for.
Whenever I want to store these values I make use of TeaCommerce.Base.UpdateOrderProperty because that updates the properties that will be read by the teaCommerceAdminOrder.xslt (as per the starter kit).
The Order properties Email, FirstName & LastName seem a little redundant or am I wrong?
No, they are not redundant as they are used for the payment gateways. It's just a way to secure the data, so they can be freezed when the order is finalized.
Its also for the UI to work in Tea Commerce - like the order list in the back-end. We have a column with the customers name and you can search by customer name. So if we dont know what the property alias is - we cant do those things - and we want to! :)
Order properties (Email, FirstName, LastName)
The Order class has Email, FirstName & LastName properties although I'm not sure what they are used for.
Whenever I want to store these values I make use of TeaCommerce.Base.UpdateOrderProperty because that updates the properties that will be read by the teaCommerceAdminOrder.xslt (as per the starter kit).
The Order properties Email, FirstName & LastName seem a little redundant or am I wrong?
Regards,
Matt
Hi Matt,
No, they are not redundant as they are used for the payment gateways. It's just a way to secure the data, so they can be freezed when the order is finalized.
/Rune
Ah, so generally speaking I should be setting these properties?
Matt
Yes, they must be filled out. :)
/Rune
Hi Matt
Its also for the UI to work in Tea Commerce - like the order list in the back-end. We have a column with the customers name and you can search by customer name. So if we dont know what the property alias is - we cant do those things - and we want to! :)
Kind regards
Anders
OK, cool.
I best get on to it. :)
is working on a reply...