Inconsistent behaviour of getStockItem() and getStockData()

[GamesmenJordan]

Preconditions and environment

Magento version 2.4.5 (tested)

Create simple observer for event catalog_product_save_before with the following execute method:

public function execute(\Magento\Framework\Event\Observer $observer) {
        $product = $observer->getProduct();
        $stockItem = $product->getStockItem();
        $stockData = $product->getStockData();
        return; //set breakpoint here
}

Steps to reproduce

1. Save a product in the Admin portal
2. Observe that $stockData will be populated with the stock item object, but $stockItem will be null
3. Save a product via the REST API
4. Observe that $stockItem will be populated with the stock item object, but now $stockData will be null

Expected result

Both getStockData() or getStockItem() should behave consistently regardless of how the product is saved, likely both returning the data or one function becoming an alias for the other.

Actual result

1. getStockData() only returns the stock item object if the product was saved via the admin portal UI, otherwise returning null.
2. getStockItem() only returns the stock item object if the product was saved via the REST API, otherwise returning null.

Both functions return the same stock item object in their respective scenarios.

Additional information

No response

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 @GamesmenJordan. 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.

[Usik2203]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @Usik2203. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @Usik2203, here is your Magento Instance: https://b55f65cec7cab462da44be1f0fd30e6d.instances-prod.magento-community.engineering
Admin access: https://b55f65cec7cab462da44be1f0fd30e6d.instances-prod.magento-community.engineering/admin_ef23
Login: 2392df2a
Password: 830a1bd32327

[m2-assistant]

Hi @engcom-Hotel. 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-Hotel]

Hello @GamesmenJordan,

Thanks for the report and collaboration!

We have tried to reproduce the issue in Magento 2.4-develop branch but it seems the issue is not reproducible for us. We have made an Observer in order to reproduce the issue.

Please find below the same as a reference:

Magz.zip

We request you to please review the steps to reproduce and let us know if anything is missed.

Thanks

[engcom-Hotel]

Dear @GamesmenJordan,

We have noticed that this issue has not been updated for a long time. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards