-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
REST API Missing Product_Option values for Order Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326
Comments
I am also seeing this issue with 2.1.4 |
@maultby Hi. Thanks for your report. The internal ticket was created MAGETWO-70532 |
Same issue here.... does anyone have a workaround or "quick-fix"? Would be great. |
@maultby, thank you for your report. |
Hi this is very important issue and we would appreciate if fixed in next 2.1 version :) |
Looks like it has been discussed previously but rejected... |
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326 - Extracted setting product options to separate class - Added product options setter for order items collection - Covered changed by API functional test
…der Items in salesOrderManagementV1 and salesOrderItemRepositoryV1 #9326 - Added product options merger
Hi @maultby. Thank you for your report and collaboration! The issue was fixed by Magento team. The fix was delivered into The fix will be available with the upcoming |
As mentioned in #9378
This is still the case which means when requesting |
I am using the magento 2.3.5 but still I didnt see the product custom options in the response . |
Any news on this? Both the orders/{order_id} and the orders/items/{item_id} return a list of option_values but they are keys to another table. It would be ideal to get the option string.
Or is there another way of retrieving this info for each order items? |
Any update on product_option. We are also facing the same difficulty to get the product_option labels and selected values. |
2.4.3 still getting option id and option value ( id ) too |
Still not getting product_options from the endpoint |
Preconditions
Mag CE 2.1.5
PHP 5.6.19
MySQL 5.7.11
Steps to reproduce
In Mag Admin create new Bundle product, add Bundle Items to product, set Ship Bundle Items option to Separately.
In Mag Admin create new Bundle product, add Bundle Items to product, set Ship Bundle Items option to Together.
Create and Save a separate Sales Order for each newly added Bundle Product.
Use Swagger or another development app to call salesOrderRepositoryV1 GET /V1/orders for each Sale Order and return the response body. Note that the response body model shows product_option with Order Items structure. But the REST response does not contain the product_option property and its values. The same missing content occurs with salesOrderItemRepositoryV1 GET /V1/orders/items/{id}.
When catalogProductRepositoryV1 GET /V1/products/{sku} is called for the Bundle products the response body correctly shows custom_attributes{"attribute_code": "shipment_type","value": "0"}
With Mag V1.9 SOAP API product_options is populated and the critical value shipment_type is shown. This value is critical for controlling how the sales order is to be handled in our receiving systems.
Expected result
REST API response body property product_option should be populated with values that include shipment_type.
Actual result
REST API response body property product_option is not included in response body despite the model_schema showing it and the order containing bundle product with shipment_type.
It is not possible to work around this by getting the product details during order item get because the Ship Bundle Items option may not be the same as when the order was created.
This is a show stopper for our integration project.
The text was updated successfully, but these errors were encountered: