Setting up item price to accept more than two decimal places.

(0) Share

Report

Posted on by James Rodgers

When setting up an item price in the inventory in AX, it will automatically round up to the hundredth place. I need to have AX allow me to enter a number with a digit in the ten thousandths palce.

EX:

price: 1.0087 gets changed to 1.01

I need AX to accept the 1.0087 price.

Thank you.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Community Member on at

Like (1)

Report

Hi James,
The price fields on the inventTable form (Base Purchase price, Base cost price, Base sales price) are stored in table: inventTableModule. The field is called "price" which has an extended data type of price.
Navigate to AOT > Data Dictionary > Extended Data Types > Price
Change the NoOfDecimals property to 4.
Kind regards.

Was this reply helpful? Yes No
James Rodgers on at

Like (0)

Report

That was it. Thank you for your help and quick response.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

No problem James. One thing to be careful about however: Any field that uses this extended data type will now take 4 digits so make sure to cross reference that EDT to other fields in the database...
:)

Was this reply helpful? Yes No
James Rodgers on at

Like (0)

Report

Can you elaborate a little more on this. I am very new to using AX or any similar software.
I did realize that I had to change the unit price to four digits for the PO's too. Is this what you are talking about?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

[quote user="James Rodgers"]
Can you elaborate a little more on this. I am very new to using AX or any similar software.
I did realize that I had to change the unit price to four digits for the PO's too. Is this what you are talking about?
[/quote]
If you look at the inventTableModule > Price properties, you can see that the ExtendedDataType is set to Price. By changing the NoOfDecimals property of that EDT, you will be changing every field that is assigned that EDT... Meaning every field will now be extended to 4 decimal places.
You have to be careful when changing common EDT's that are used in a bunch of different tables. For example ItemId.
In some cases you will not want to extend the decimal places for all tables that have a field using that EDT. A good solution for this is to create your own EDT and assign that to the field instead of modifying the existing EDT. This way the base EDT will not be affected.
I hope this makes sense. :)

Was this reply helpful? Yes No
James Rodgers on at

Like (0)

Report

Yes, that does make sense thank you.
It sounds like setting up a new EDT requires coding in X++. If so, I probably will have to just leave it as is. I don't see any problems with it so far.
Thank you again for your help.

Was this reply helpful? Yes No
Denis Patrakov on at

Like (0)

Report

[quote user="James Rodgers"]When setting up an item price in the inventory in AX, it will automatically round up to the hundredth place.[/quote]There's also a field PriceUnit (quantity for which the price is entered), in your case you should set the price to 100.87 and price unit to 100.

Was this reply helpful? Yes No
Shafeeque P. 6,533 Moderator on at

Like (0)

Report

The decimals are fine on my back office client. However, the POS still shows only two decimals places. Changing the Price EDT dint help.

I updated the price rounding rule of our base base currency ( GL--> Setup --> Currencies--> Rounding Rules) to 0.0010 and pushed the data to store. Now the POS is showing 3 decimals in all price fields. However, this has given raise to another issue in line discount. I am going to update decimals of Realbase EDT to 3 and check if this can permanently resolve the issue.

Was this reply helpful? Yes No
Vishal Jevtani 278 on at

Like (0)

Report

Hi Shafeeque,

Can you tell me what kind of problems you faced after setting the roundoff edt to 4 digits? also what wast the solution to this problem? I have a similar requirement.

Was this reply helpful? Yes No