Hierarchy Per Period Calculation Metrics creation fails for OOTB and custom TSV due to Work Effort Unit mismatch
search cancel

Hierarchy Per Period Calculation Metrics creation fails for OOTB and custom TSV due to Work Effort Unit mismatch

book

Article ID: 389096

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Creating a Calculation Metric on Hierarchy on OOTB TSV labor_act (Hours) and a custom TSV field (Hours) does not work as Clarity is also matching workEffortUnit Extended Type attribute which is null for all custom TSVs. OOTB TSVs like labor_act have an invisible Extended Type set to Seconds. Custom TSVs have no workEffortUnit set, and it is null, which causes the validation failure.

STEPS TO REPRODUCE: 

  1. Connect to Clarity – Administration – Studio – Objects – Investment
  2. Create a new custom field Test, type Time Varying – set Time varying unit conversion to Hours
  3. Add API Attribute ID
  4. Save
  5. Now go to Hierarchies and create a new hierarchy, type Investment and add a couple of projects
  6. Open the Hierarchy - View Options - Manage Metrics – Calculation – New Metric
  7. Add a Name, Metric Type = Per Period , Metric One = Actuals , Operation = Substract, Metric Two = Test
  8. Click on Create

Expected Results: The Calculation Metric to be added as the labor actual units are in Hours and the new custom TSV unit is in Hours and they are set identically

Actual Results: Error in UI “Metric One and Metric Two must be of the same data type.”, message in logs is Metric One and Metric Two must have same Work Effort Unit.

Error in logs:

ERROR 2025-02-25 06:59:49,928 [http-nio-1630-exec-570] object.HierarchyCalcAttributeInstance (clarity:admin:5557074__C291F80C-9869-46E1-AB5D-8DB210842CEA:PPM_REST_API) (0c35786b-b947-4b9d-b1bd-be2939d706bc) Metric One and Metric Two must have same Work Effort Unit.

ERROR 2025-02-25 06:59:49,929 [http-nio-1630-exec-570] rest.validation (clarity:admin:5557074__C291F80C-9869-46E1-AB5D-8DB210842CEA:PPM_REST_API) (0c35786b-b947-4b9d-b1bd-be2939d706bc) ODFResourceProvider :: Could not create resource. Object code alias: [ requestUrl: http://XXXXXXXXXXXXXXXX/ppm/rest/v1/private/hierarchyCalcAttributes , _restResourceName : hierarchyCalcAttributes , _id : null , _parentInfo : null , _apiVersion : v1 , _includeLinksArray : true , _contextId : -1 , _hierarchyId : 5003002 , _isGroupBy : false , _isPartition : false]

ERROR 2025-02-25 06:59:49,929 [http-nio-1630-exec-570] rest.validation (clarity:admin:5557074__C291F80C-9869-46E1-AB5D-8DB210842CEA:PPM_REST_API) (0c35786b-b947-4b9d-b1bd-be2939d706bc) ExceptionInfo ::  Could not create resource. Resource name: hierarchyCalcAttributes. Error code: odf.hierarchyMismatchedAttributes Error message: Metric One and Metric Two must be of the same data type.

Note: Comparing labor_act to a custom TSV in Seconds will also not work

Environment

Clarity 16.2.3, 16.3.0, 16.3.1

Cause

DE166801 (Works as Designed)

Resolution

  • This is due to Software Limitation due to the fact custom TSV do not have a WorkEffortUnit set up and without this they comparison will not be done in correct units.
  • Feel free to submit this with Product Management as an idea to provide this functionality going forward