Cyclic reference in project causing high temp utilization
search cancel

Cyclic reference in project causing high temp utilization

book

Article ID: 408299

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity FedRAMP Clarity PPM On Premise

Issue/Introduction

Cyclic reference in project causing high temp utilization This query is generating due to feature Include Actuals from Children in Cost Plan/Budget

WITH RECURSIVE inv_hier AS ( SELECT id,parent_id,odf_object_code FROM inv_investments WHERE id in(5851311, 5243934)UNION ALL SELECT e.id,e.parent_id,e.odf_object_code FROM inv_investments e JOIN inv_hier h ON e.id = h.parent_id)UPDATE fin_plan sp SET actuals_out_of_date = 1 FROM inv_hier h WHERE p.object_id = h.id AND p.object_code = h.odf_object_code AND p.ACTUAL_FROM_CHILDREN = 1

Steps to Reproduce: 

  1. Login to Clarity MUX as Project Manager rights 
  2. Create 2 Projects Project1, Project2. 
  3. Configure Parent column in the project list grid.
  4. Make "Project1" parent as "Project2"
  5. Make "Project2" parent as "Project1".

Expected Results: Clarity should  throw an error that it will form a cyclic reference.

Actual Results: Clarity's business logic should stop when executing Step 5 as it will create cyclic reference. 

Environment

Clarity 16.2.3, 16.3.3, 16.4.0

Cause

DE174864

Resolution

Fixed in

  • Clarity 16.4.1 

Additional Information

  • One of the implications of allowing cyclic reference causes "Update Financial Plan Actuals and Forecast job" Actual causes the job to run forever when "Include Actuals from Children" is selected on any cost plan.