Any combination of valid field names from the guests and/or address tables

A new button appears on either Checkout.aspx or Checkout2.aspx (when using checkout steps) when you set a purchaser. The button has the default wording of Edit this Purchaser which can be changed in the markup for the page. This button allows easy access for the purchaser to edit the guest record.

Fields in the guest record for the purchaser in an E-Commerce sale can be handled differently from fields in the guest record for guests attached to products. This works in the same manner as ForceEditFields except that they only affect the guest who is set as the purchaser in the sale. These Purchaser keys can take the same values as the corresponding Guest keys. Additional configuration can be done in the dynamicControls.xml file. Each field/section in that file now has a <Required_purch> . . . </Required_purch> setting which can be set to 1 (TRUE) or 0 (FALSE). Setting this to 1 makes it so that the field is required if the purchaser edits their guest record.

Also, if the purchaser guest record is missing any of the fields set in the PurchaserForceEditFields key, the message configured with the control asp:label id="lblFieldsRequired" displays. The default wording for this control is, “Please click on Edit Purchaser to edit all the required fields.” This can be changed in the markup for the page.

 

PurchaserForceEditFields = first_name, last_name, address, city, state, zipcode, phone, email, username, password