REST API Missing some Product_Option values for Order Items

[suncofamily]

Preconditions and environment

• Magento version 2.4.6

Steps to reproduce

1. Create a Bundle product
2. Create a sales order with bundle product(s)
3. There is bundle_selection_attributes in product_options column of sales_order_item table with the bundle item (parent and child)
4. Call POST /V1/orders API to update order
5. The bundle_selection_attributes will be missing. (note: other key/value will be missing too)
6. This will let the order detail page can not be opened
7. This will make the order shipment can not be created

Expected result

1. POST API needs to remain the before data of product_options column in sales_order_item table

Actual result

• before data

{"info_buyRequest":{"uenc":"aHR0cHM6Ly9ldS5zeW5vZWMtZGV2LnN5bm8vZGVfZGUvcnQyNjAwLXByb21vLmh0bWw~","product":"257","selected_configurable_option":"","related_product":"","item":"257","bundle_option":{"17":"20","18":"22"},"qty":"1"},"bundle_options":{"17":{"option_id":"17","label":"xxx","value":[{"title":"xxx","qty":"1","price":159}]},"18":{"option_id":"18","label":"yyy","value":[{"title":"yyy","qty":"1","price":10}]}},"product_calculations":1,"shipment_type":"1"}

• after data
  • parent {"info_buyRequest":{"qty":1,"bundle_option":{"17":[20],"18":[22]},"bundle_option_qty":{"17":1,"18":1}}}
  • child []

Additional information

1. Is it same as REST API Missing Product_Option values for Order Items #37567?

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @suncofamily. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://97d212ea8d1b0aad1417404b9cf4c4db.instances-prod.magento-community.engineering
Admin access: https://97d212ea8d1b0aad1417404b9cf4c4db.instances-prod.magento-community.engineering/admin_69f6
Login: 34aa7dba
Password: 48b1584311cc

[engcom-Bravo]

Hi @suncofamily,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Create a Bundle product
• Create a sales order with bundle product(s)
• There is bundle_selection_attributes in product_options column of sales_order_item table with the bundle item (parent and child)
• Call POST /V1/orders API to update order
• The bundle_selection_attributes will be missing. (note: other key/value will be missing too)
• This will let the order detail page can not be opened
• This will make the order shipment can not be created

After calling REST API we are able to open order detail page and order shipment page and we are able to create.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[suncofamily]

Hi @engcom-Bravo

I found the problem:

1. Get /V1/orders/{entity_id} API， and get the response
2. Modify this response

$response["base_currency_code"] = "EUR"

3. Use this whole response to call POST /V1/orders API

$requestBody = ["entity" => $response]

4. After update success, I found some key-value missing in the product_options in sales_order_item table

And if I do this:

1. Get /V1/orders/{entity_id} API， and get the response
2. Modify this response

$response["base_currency_code"] = "EUR"
unset($response["items"]);

3. Use this whole response to call POST /V1/orders API

$requestBody = ["entity" => $response]

4. After update success, there is no problem in the product_options in sales_order_item table

Do you know why this happened?
I think the original order response is the same as all the order detail, but it doesn't seem to be the case

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.