• State Not Answered
  • Replies 1 reply
  • Subscribers 11 subscribers
  • Views 2273 views
  • Users 0 members are here
Options
Related

Decimal data type doesn't support double precision numbers

david.creech
Offline

I need to store both large and small numbers in a property of type Decimal. I set the Precision to the maximum of 38 and set the scale to 19. I expected that I could store numbers with 38 digits and 19 of those after the decimal point.

Instead what I find is that the maximum digits I can enter and save is 29. More digits causes a Conversion Overflow error. 

Additionally, after saving the item the number is rounded such that there are only 17 digits of precision. For example, if I enter 1234567890.1234567890123456789, after saving it is truncated to 1234567890.1234567000000000000. Similarly, if I set Precision to 38 and Scale to 0 I can enter 12345678901234567890123456789, but it is rounded to 12345678901234568000000000000.

Additionally, changing the data type to Float has similar behavior, but entering 1234567890.1234567890123456789 results in 1234567890.1234567 being stored.

I am using 12.0 SP9. Is there any way to store Double precision data in a Decimal data type in Aras? 

  • 0 Offline

    Update: Changing the value directly in SQL server works as it should. The column is set up properly with Precision 38 and Scale 19, and I can store values with 19 digits before the decimal and 19 digits after. However Aras gives a Conversion Overflow error in search grids and the item's edit form. With 10 or less digits before the decimal there is no conversion overvlow error, but the values are still truncated and padded with zeros. 

    Can anyone confirm if you see the same behavior in SP9 or later versions?