-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order CustomValuesXml #5250
Comments
Any more thoughts on this change ? |
See also #3304 |
…etails page to under the Payment Details
Closed #5250 |
Suggestion that there now be a case to add a Type or DIsplay Location field and make it a Tuple <DisplayLocation, Key, Value>
In a new Shipping plugin the Service Location for pickup of the order package with associated details as well as a customer Reciept Number are stored as customer order values - The details are now displayed under Payment but would be better if displayed under shipping |
nopCommerce version: All
Regards the attribute order.CustomValuesXml
On the Customer Order Details page, the decoded values are associated with and displayed under the Billing Address heading
In the Order PDF the values are displayed separately under the Payment Method Details
In Admin Order Details the Custom Values are displayed separately under the Payment Method details
I use order.CustomValuesXml for storing details about the payment either:
The Payment Method type (in the case where there are multiple payment types for the one payment method)
For other payment methods order.CustomValuesXml is used to store a Payment Receipt number
I dont know how others may use it ?
I also do not know if there is a reason why order.CustomValuesXml are associated with the Billing Address on the Customer Order Details page ?
This attribute is more likely to be used to store information about the order rather than details related to the billing address.
I would like to recommend that the display of the order.CustomValuesXml be moved on the Customer Order Details page to under the Payment Details so that it is standardised in all three locations.
The text was updated successfully, but these errors were encountered: