Credit doesn't recognize amount after comma

[gerben86]

When I enter an amount with decimals (like 2,50) in the field "Adjustment Refund" while making a Credit Memo the amount on the real credit memo is without decimals (2,00). So the Credit Memo isn't in line with the real credit amount.

Preconditions

1. Magento 2.1.10

Steps to reproduce

1. Create a Credit Memo for an order
2. Enter an amount with decimals (by example 1,23) in the field Adjustment Refund
3. Create an offline payment (finish credit memo)

Expected result

1. The credit memo should show the amount of 1,23 in the field "Adjustment Refund" on the Credit Memo overview

Actual result

1. The credit memo should show the amount of 1,00 in the field "Adjustment Refund" on the Credit Memo overview

I'm using a comma as decimal seperator, because my local language is dutch.

[magento-engcom-team]

@gerben86, thank you for your report.
We've acknowledged the issue and added to our backlog.

[vijay-wagento]

This is working fine in magento 2.2. Verified at #dmcdindia

[magento-engcom-team]

@vijay-wagento thank you for joining. Please accept team invitation here and self-assign the issue.

[magento-engcom-team]

@gerben86 Could you please verify that it works as expected for you now?

[gerben86]

@magento-engcom-team , Unfortunally the issue still exist (Magento 2.2.4) See printscreens.
Adding adjustment amounts:

Decimals are gone after clicking on "Update Totals":

[GovindaSharma]

#MM19IN

[magento-engcom-team]

Hi @tonytrinh218. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[tonytrinh218]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @tonytrinh218. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @tonytrinh218, here is your Magento instance.
Admin access: https://i-13851-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[m2-assistant]

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

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-30172 were created

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

[sedero]

The problem is the trim function on Magento/module-sales/Model/Order/Creditmemo.php

setAdjustmentPositive / setAdjustmentNegative

$amount = trim($amount);

[m2-assistant]

Hi @sergiy-v. 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.

[magento-engcom-team]

Hi @gerben86. Thank you for your report.
The issue has been fixed in #27343 by @sergiy-v in 2.4-develop branch
Related commit(s):

• 4046760db00a93d147b3b40609c1c0b6cdda8ca0

The fix will be available with the upcoming 2.4.0 release.