Rest API products-render-info return wrong final price for logged in customer

manhtranisobar commented 2 years ago

Preconditions and environment

Magento version: 2.4.4
B2B modules enabled

Steps to reproduce

Create new product SKU A, base price 100 $
Setup tier price for product A with customer group B, qty 1, price 90$
Create new customer account C and assign to customer group B (Ex: Wholesale)
Call API get customer token for customer C
Use customer token to call API products-render-info (https://magento.redoc.ly/2.4.4-customer/tag/products-render-info)

Expected result

Final price is 90$

Actual result

Final price is 100$

Additional information

There is no issue for other products with Tier price set to All Groups (Customer). Tier price is displayed as the final price in Api response when admin access token is used

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[bot] commented 2 years ago

Hi @manhtranisobar. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

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

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.

: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, join the Community Contributions Triage session to discuss the appropriate ticket.

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

m2-assistant[bot] commented 2 years ago

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: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components 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-November commented 2 years ago

Verified the issue on Magento 2.4-develop branch with B2B features enabled and the issue is reproducible. Hence updating description and confirming the issue.

github-jira-sync-bot commented 2 years ago

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-5979 is successfully created for this GitHub issue.

m2-assistant[bot] commented 2 years ago

:white_check_mark: Confirmed by @engcom-November. Thank you for verifying the issue.
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.

manhtranisobar commented 2 years ago

Hi @engcom-November Can I know when we have patch to fix this issue?

Kannakiraj123 commented 1 year ago

@magento I am working on this

Kannakiraj123 commented 1 year ago

Find below code fix the issue

1.In product collection pass customerGroupID

$productCollection->addPriceData($customerGroupId);

2.For Product rendering in foreach loop pass $item with customerGroupId

$item->setCustomerGroupId($customerGroupId);

foreach ($productCollection as $item) {
  $productRenderInfo = $this->productRenderFactory->create();
  $productRenderInfo->setStoreId($storeId);
  $productRenderInfo->setCurrencyCode($currencyCode);
  $item->setCustomerGroupId($customerGroupId);
  $this->productRenderCollectorComposite->collect($item, $productRenderInfo);
  $items[$item->getId()] = $productRenderInfo;
}

magento / magento2