Product price updated using Manage Base Price API is not updating in Store front Catalog Search Results page and Admin panel

[engcom-November]

Preconditions (*)

1. Magento 2.4-develop

Steps to reproduce (*)

1. Generate Admin access token using POST request: storeurl/rest/default/V1/integration/admin/token
2. Send POST API request for sync product: storeurl/rest/V1/products/base-prices. (Update Price using below Payload): Payload:

{
  "prices": [
    {
      "price": 85.67,
      "store_id": 1,
      "sku": "Test PRice"
    }
  ]
}

3. Reindex and clear cache
4. Navigate to Front-end -> Verify Price in Search Results page and Product Details page Issue 1: Price updated through API is getting updated in Front-end Product Details page only but not getting updated in Catalog Search Results page and Admin - Products page
5. Navigate to Admin - Catalog - Products - Edit same Product - Update new price say ex: 90 and save
6. Reindex and clear cache
7. Navigate to front-end - Product Details page Issue 2: New Price updated from Admin panel is not getting updated in Front-end product details page (Old value saved using API is displayed in Front-end Product Details page)

Expected result (*)

Base price should be updated in both Search Results page, Product Details page and Admin -> Catalog - > Products page

Actual result (*)

Issue 1. Price updated through API is getting updated in Front-end Product Details page only but not getting updated in Catalog Search Results page and Admin - Products page

Updated price through API : 85.67 is updated in Product Details page only

Issue 2: New Price updated from Admin panel is not getting updated in Front-end product details page (Old value saved using API is displayed in Front-end Product Details page)

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] 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[bot]]

Hi @engcom-November. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-November Thank you for verifying the issue. Based on the provided information internal tickets MC-43069 were created

Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-November Thank you for verifying the issue. Based on the provided information internal tickets MC-43069 were created

Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[nuzil]

Hi @engcom-November I have a strong feeling issue is connected with this changes: https://github.com/magento/magento2/pull/32371

Can you please try with patch from this PR and tell if its still exists?

Or try directly on PR test Magento instance

[m2-assistant[bot]]

Hi @nuzil. Thank you for working on this issue. Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.magento.com/browse/AC-708

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-708

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-November, here is your Magento Instance: https://a171f743d887fc691cb9c996c4d13ab2.instances.magento-community.engineering Admin access: https://a171f743d887fc691cb9c996c4d13ab2.instances.magento-community.engineering/admin_3c79 Login: 48f595a2 Password: 901e3a7ca0e6

[engcom-November]

This issue is no more reproducible on Magento 2.4-develop instance.