Timesheet Total Hours Lose Decimal Precision and Round to Whole Numbers in MUX Reporting Grid

Products

• Clarity PPM SaaS
• Clarity FedRAMP
• Clarity PPM On Premise

Issue/Introduction

When viewing timesheet total hours within a Modern UX (MUX) Reporting grid, widget, or Ad Hoc layout, the field values lose their decimal precision and incorrectly round to the nearest whole integer.

Steps to Reproduce: 

1. Navigate to the MUX Report Designer and create a new Data Provider utilizing the Timesheet object.
2. Create a new report template using this newly generated Data Provider.
3. Add a data grid or widget to the report canvas and include the following columns: Resource, Period, and Total.
4. Post timesheets for a resource across two separate periods containing decimal hours (for example, Week 1 with 7.25 hours and Week 2 with 7.5 hours).
5. Run the report and observe the values rendered in the grid.

Expected Results: The grid displays exact hours reflecting the entered decimal precision (e.g., 7.25 and 7.50).

Actual Results: The grid values round up or down to whole numbers (e.g., 7.25 truncates to 7.00, while 7.5 rounds to 8.00), discarding precision.

Environment

Clarity 16.4.1, 16.4.2

Cause

DE208873

Resolution

DE208873, in review by Engineering

Additional Information

Workaround: The actual underlying database values remain uncorrupted and accurate to their true decimal format. Because the truncation occurs entirely during the OData-to-Grid visualization layer, there is no direct UI switch within the MUX Report Designer that can restore the decimals. If the exact figures are needed urgently, utilize one of the following alternate data-extraction methods:

• Utilize XOG or REST APIs: Extract the timesheet data directly via the XML Open Gateway (XOG) or standard MUX REST endpoints. These channels parse the direct floating-point attributes (total/v_total) safely outside of the impacted defect.