Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / decimals on Qty
Microsoft Dynamics AX (Archived)

decimals on Qty

(0) ShareShare
ReportReport
Posted on by Ronald Raes 70

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

  • Ronald Raes Profile Picture
    Ronald Raes 70 on at
    Re: decimals on Qty

    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).

  • Brandon George Profile Picture
    Brandon George 2,632 on at
    Re: decimals on Qty

    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.

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: decimals on Qty

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

  • Muhammad Afsar Khan Profile Picture
    Muhammad Afsar Khan 2,676 on at
    Re: decimals on Qty

    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

  • David Lawson Profile Picture
    David Lawson 80 on at
    Re: decimals on Qty

    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.

  • Celeste Profile Picture
    Celeste 263 on at
    Re: decimals on Qty

    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,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,622 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,354 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans