Timesheet options Decimal Places is not honoring the configuration
search cancel

Timesheet options Decimal Places is not honoring the configuration

book

Article ID: 117821

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction


Timesheet options Decimal Places is not honoring the configuration 

Steps to Reproduce:

1. In timesheet options : 
Decimal Places=2 
Display Unit=Hours
2. In Classic PPM enter timesheet for a resource: 
Enter for example 1.138.
Click on Save

2.1. Observe UI.
UI shows 1.14. 

2.2. Query the DB: select * from prtimeentry order by prmodtime desc (check first record)

DB stores 4096.7999999999993 

3. In New UX do the same and enter the same value 
Same results 

Actual Results:
In My timesheet options I set Decimal Places=2. It is not honoring the configuration; maybe the configuration is for display only; not entering values.
 
Expected Results:
We should honor the setting to only allow entering the values based on the configuration.
In the DB, it really should store it with a decimal precision of two, just as it's being displayed on the timesheet. 

Environment

Release:
Component: ODTMM

Cause

Caused by DE44895

Resolution

This is per design. This is how our numbers viewing/editing is designed.