web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Purchased item rounding

(0) ShareShare
ReportReport
Posted on by

DAX is rounding everything to 2 decimal places prior to the multiple which leads to issues on our POs and in Accounts Payable.  For example, if we are buy 1000 pcs of a component that costs $0.004 each DAX rounds to $0.00 and the PO will say 1000 pcs for $0.00.  If the component costs $0.005 each DAX rounds to $0.01 so the PO says 1000 pcs for $10.00 vs. the $5.00 it actually costs.

We have lots of work arounds for this but is there a true fix anyone knows of?  It seems like there may be a setup setting that we missed.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Ludwig Reinhard Profile Picture
    Microsoft Employee on at

    Hi Elena, I also experienced this issue many times. The only "workaround" that really helped was not setting up prices in 100s/1000s. Please check if you can setup prices per pcs. If you want to purchase the items in quantities of 100s/1000s... you can define a default purchase quantity but avoid those rounding issue. Hope it helps, Ludwig

  • Yohann Rolland Axcible Profile Picture
    3,111 on at

    Hi,

    It's indeed a strong constraint, you cannot add more than 2 digits.

    You need to setup a price unit for setting up your price.

    Example : your component si up to 0,004 each. So setup your price to 0,04 for a price unit setup to 10.

    You purchase 10, your price will be 0,04.

    You purchase 1, your price will be 0,004.

    In that case Ax will round the price for displaying but stored in the table it should be the correct value.

  • Community Member Profile Picture
    on at

    Hi Elena, there is two solution for it but remember first solution is not advisable. I hope if Microsoft look into this and issue any hotfix for it.

    1) with the help of developer you need to change the extended data type for currency / values from 2 to 3 in your case and it will resolve the issue but remember this will effect the whole system.

    2) make a unit conversion which will lead you to 2 decimal place. but again you will have an issue in consumption where the qty is less. but if the qty is more then no issue. I hope you get it what I mean.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans