Just another UI Inconsistency I believ but thought I would mention it.
This appears to effect only calculated fields, where the field shows more decimal places than the fields precision setting
See screen shots, the only time it becomes an issue is with rounding.
Solved! Go to Solution.
Could you send a screen shot of the Unit Price field configuration from the Grid?
Your computed field is currently "CURRENT_COST + CURRENT COST" and I'm thinking that you want QUANITY in the formula. The system will not round as it does not know how to round up or down. In the final formula for your computed field try ROUND(ITEM,2) to round up to the nearest two decimal points. Replace ITEM with the rest of your formula.
Well the full formula is CURRENT_COST =CURRENT_COST * MARK_UP/100.
But using the Round Function solved the extra decimal place issue nicely, thank you. I figured the issue was that the precision was getting ignored because it is a computed field. Using the round function forces two decimal places and rounds up correctly.
With that in mind is there a reference to valid functions that can be used in calculated fields. I have seen some in examples both on the wiki help and the blogs (Calculated fields Small but Powerful) but there doesn't seem to be a complete reference. I believe it is most likely standard HTML functions but not sure.
Any thoughs on the unexpected decimal places in the BOM Costing record?
It seems there is some background calculation or process occurring to calculate the unit cost in the parent item bom from the child items sourcine default cost record?
Thanks again for your help
You can go to http://w3schools.com and use the reference material provided for both html and SQL.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.