SQL Curve Totals are displaying wrong in MUX Staffing after a Time Slicing rollover

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

In MUX Staff Grid and Allocations by Resources we can see the Total row is 0 for all resources which is incorrect for the aggregation

STEPS TO REPRODUCE:

1. Connect to Clarity before Time Slice Rollover
2. Open Staffing Grid with Per Period Metrics added with Totals on Allocation
3. Note numbers totals display correctly
4. Now run Time Slicing job to perform a rollover
5. Once the job is complete and refresh the Staff page

Expected Results: The Allocation Totals to be the same as prior to the rollover

Actual Results: The Allocation Totals are nulled out for all resources (show as 0)

Note: this may occur on other metrics aside from Allocation like Availability and Hard Allocation

Another symptom of the same issue - the Totals display data which is wrong, significantly higher than expected values, only when the Unit of Measure is set to %Availability or FTE

Environment

Clarity 16.2.2

Cause

DE153966

Resolution

DE153966 is fixed in 16.3.0 (Targeted to release November 2024) and also backported to 16.2.3 patch 1 

Workaround:

Run Time Slicing Sync job with force flag on. 

Note: On large systems this job may take a while, so we recommend running it after hours

If your dataset is very large, use the below alternate workaround:

1. On the database, run the query (this example is for Allocation):
   update prteam set odf_nk_odf_pralloccurve  = null where (odf_nk_odf_pralloccurve).curve_sum = 0
2. Run the Time Slicing Sync as regular job, without the force option

Additional Information

• Once the fix is applied with 16.3.0, 16.2.3.1, there will be no further issues with Totals after rollover.
• For preexisting data discrepancies - please apply the workaround to run the Time Slicing Sync job with force flag on