Decimal rounding of the physical updating quantity is incorrect

(3) Share

Report

Posted on by Adis

6,048 Super User 2025 Season 2

Dear all,

We have an issue where we create an intercompany customer invoice (project related) which works fine.

When we want to post the corresponding intercompany pending vendor invoice it throws an error:

"Decimal rounding of the physical updating quantity is incorrect"

This can be solved by increasing this number here:

However, I am a bit afraid to increase the number from 3 to 8 as I am not aware of the impact when increasing the decimal precision?

Since you cant decrease the decimal precision, what are the drawbacks if you have a higher number? I guess there are some, otherwise, why not increase the precision to a maximum?

Thanks in advance, Adis

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (7)

Answers (0)

Jonas "Jones" Melgaard 4,899 Most Valuable Professional on at

Like (1)

Report

I feel that you should never have more than 2 decimals in an hour unit, so I'd be a bit hesitant increasing it to 8. I'm afraid it will be messy....

Do you know how many decimals the pending vendor invoice has?

Edit: It mentions physical update. Do you post hours to inventory? Dumb question from my side, sorry

Was this reply helpful? Yes No
André Arnaud de Cal... 300,911 Super User 2025 Season 2 on at

Like (1)

Report

Hi Adis,

Do you have technical details why the error pops up? How many decimals are used in the hour field that causes the error? Did you test in a non-production environment if increasing the decimals on the unit will solve this?

Was this reply helpful? Yes No
Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Hello,

@Jonas:

I was also wondering about the physical mentioning. The entries are coming from the timesheet and its posted via procurement categories, not items.

And no, its never a dumb question. I am really asking the simpliest question sometimes because I want to make sure that I got it right 100% and didnt miss anything.

@André:

That was my 2nd thought to debug it with a developer. I thought maybe someone knows by heart why this pops up.

A colleague tested it in a sandbox with 6 digits and it works, previously it was 3 digits, maybe it also works with 4 or 5, this is to be figured out by me.

I will keep you posted about the outcome of the debugging.

Kind regards, Adis

Was this reply helpful? Yes No
Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

We debugged the issue:

Note from developer:

"

with comparison _qty ==decRound(_qty, UnitOfMeasure::unitOfMeasureDecimalPrecision(UnitOfMeasure::unitOfMeasureIdBySymbol(_unit))),
where _qty = 0.366667 and _unit = h.

In this case UnitOfMeasure::unitOfMeasureDecimalPrecision(UnitOfMeasure::unitOfMeasureIdBySymbol(_unit) returns 2.

so comparison looks like 0.366667 == 0.37 and returns false.

"

I was expecting that the qty. is being compared to the Intercompany customer invoice, however, instead the qty. is being compared to the rounded qty. according to the decimal precision (so comparison looks like 0.366667 == 0.37 and returns false).

I would expect the qty. to be rounded by the decimal precision, not to be compared to it.

It works in Contoso. The posting in our environment works according to standard code, however, I guess the creation of the lines, during posting of the IC customer invoice, is using custom code, but I need to investigate

Will keep you posted.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Hello,

We decided to change the decimal rounding. Seems like the custom code is creating these issues as it works in Contoso.

Kind regards, Adis

Was this reply helpful? Yes No
Navneeth Nagrajan 2,407 Super User 2025 Season 2 on at

Like (1)

Report

Hi Adis,

Suggestions:

1. Have an unit defined explicitly to consider 3 decimal precisions and assign it to the product (Looks like you are dealing with fixed assets in here).

2. In addition to the first suggestion you can also consider unit conversions where the unit you need to convert to is set to 8 decimal precisions from the 3 decimal precision units through the intraclass conversions (if they are product specific if they are in the same unit class) or inter-class conversions(across different unit classes), based on the business scenario.

Note: After increasing the decimal precision to 8 it won't allow you to change the decimal precisions to 3 so would recommend being a bit careful there. Also, would recommend creating a new unit in there that would support 8 decimal precisions and one that supports 3 decimal precisions and use it accordingly. We had a similar scenario in the Fleet management space where we had to support 6 decimal precisions instead of 2 decimal precisions and we ended up having multiple units to address this challenge.

Was this reply helpful? Yes No
Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Hi Navneeth,

The unit is used in the time class and the record is coming from the Timesheets (Project Management).

I will check using another unit for the given project, maybe that would work, so if I mess up with the decimal rounding, its messed up for the newly created unit and not the default one (h) we are using.

Kind regards, Adis

Was this reply helpful? Yes No