AX calculation of the total amount:
Rounded up amount
Amount « 500,98 » is invoiced to the customer
But if we hide the line discount and use a custom field "discounted unit price":
Discounted unit price
Discounted unit price (rounded up)
In this case, since 62,62*8 <> 500,98 we're in trouble.
Hello Barclay, Thanks for your answer. We not only need to hide the discount %tage. We also need to display a unit price. But there is no such thing as a discounted unit price. Whether we create it in the interface or calculate it on the printout leads to the same result: we have to round it up, and it's not compliant with the system standard calculation. It's a complex topic, but I don't know how to explain it better than in my above example... I've investigated A LOT and my conclusion is that there is no technical solution. My wish is more to make a process adjustment, and have the business reviewing the way they maintain prices in the system. Well, if there is a technical solution, I'm still in! But I'd also like to know what functionality do my peers usually use, out of all the possibilities offered by the standard, when it comes to activate price / discounts.
Any testimony? Thanks!
Hello, I've looked a bit into using net prices, calculated using an external table dealing with discount percentage per customer. We have thousands of items and thousands of customers (not so many are grouped)... I wonder if there is any reasonnable limit to the number of trade agreement values one D365FO can deal with. I'd have something like 1 000 000 net prices. Is there any performance risk in having over 1 000 000 trade agreement line? Thanks for any feedback.
If you've found this thread useful, dive deeper into User Group community content by role