decimals on Qty

(0) Share

Report

Posted on by Ronald Raes

Hello everyone,

The customer i’m currently implementing AX for, has asked me to make a global change to the field Quantity to zero decimals. Just blocking the input of quantities with decimals by setup on units is not enough. They’re also asking to stop showing the 2 ‘.00’ decimals that you see on every Qty field throughout the application.

It is a rather unusual request, and one I’d rather not make because I fear this could have a serious impact. So I’ve been looking around on forums to try and find some input on the technical impact of this kind of change, but I have not found anything. Quite a few discussions on increasing the number of decimals, but never a decrease to zero.

Does anybody have experience with the technical issues that could arise with this kind of change?

Thank you for the feedback.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Celeste 293 on at

Like (0)

Report

If you do not want to affect the way the data is stored, I would suggest to change the NoOfDecimals property of the fields on the forms to zero. But it means you'll have to do this for all the forms...

If you change the NoOfDecimals property of the Qty extended data type in the Data Dictionary to zero, it will be saved with zero decimals in the database.

Why do they want to do this? This is certainly not a usual request. I suggest explaining to the client the impact of the change before proceeding.

Regards,

Was this reply helpful? Yes No
David Lawson 80 on at

Like (0)

Report

Ronald,

I dont think that changing the decimals does change how the data is stored.

I entered a value of 4.5 on a purch line, changed the NoOfDecimals propery on the underlying edt to 0. The Displayed value on the form became 5, the value stored in the database remained 4.5.

Changing NoOfDecimals back to 2, the displayed value was again displayed as its (correct) 4.5 value.

Was this reply helpful? Yes No
Muhammad Afsar Khan 2,676 on at

Like (0)

Report

I guess this is due to the rounding define for purchase order on GL> Setup> Currencies>Roundling rules>Purchase order. Can you please check it as well. Just set rounding rule = 0.0

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Try setting the NoOfDecimals property to zero and the MinNoOfDecimals to 0 on the form level.

Was this reply helpful? Yes No
Brandon George 2,632 on at

Like (0)

Report

I would for sure push back on this. The whole point of having a real datatype is to allow for at least 2 decimal places. Depending on precision desired, I have seen 4 and 6 decimal points.

If there is a field they don't want decimal values for, then the correct answer would be to change the datatype from real to int or int64 (depending on the version of AX).

Plus even chanigng the datatype of every field that has a Decimal is not recommend either. So for sure I would recommend pushing back on this and asking the true value, and reason why. I would be willing to bet the cost / ROI for the effort in doing this, is not work it at all.

Others are already pointing out how you can do this, however again I would strongly push back of why. Just because the client ask for it, does not mean it's right for the client.

Was this reply helpful? Yes No
Ronald Raes 70 on at

Like (0)

Report

Thanks to all for the feedback !

to answer some of your follow-up questions:

The customer's argument is that they never work with decimals on their articles. they work with the unit 'pieces', never anything else, and never use 'half a piece' so to speak.

At this point ,the system is already setup to work that way thanks to setup on units. Nr of decimals set to 0, and everything works fine. Except for the fact that every form (and reports) shows qty's like '1.00' or '5.00' instead of '1' or '5'. So at this point we're talking about a purely cosmetic issue here.

I already have functional arguments prepared to push this back, for all the reasons you guys are pointing out. In my opinion the cost of this is just too high to implement. I'm just doing due diligence and also looking for technical information. What are the options if we'd want to do it, and what is the impact of every option: change of EDT compared to changes on form level (like some of you also pointed out).

Was this reply helpful? Yes No