Plans from OBS > Investment Breakdown keeps Loading with [object Object] error

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

There is an Object error when loading plans (Investment) and Investment Breakdown uses Manager.

STEPS TO REPRODUCE:

1. Go to Modern Workspace: Plans

2. Click button 'New Plan from OBS'
a. Select Top Level Plan Node (start)
b. Navigate and select Lowest Level Plan Node (end)
c. Allow the background job: Synchronize Plan from OBS to finish

 APP message will be:  Plan Sync in Progress. This plan is temporarily locked for editing
It runs Background job: Synchronize Plan from OBS
Wait for it to finish.

3. Review the Plan > Choose Configure > Investment Breakdown > choose 'Manager' 

Expected: There should not be performance issue

Actual: It never finishes configuring and all the following are experienced:
Unable to delete or add tables [object Object]  error keeps appearing
'Investment Breakdown' section shows indefinitely: Loading data...Please wait
 

ERROR 2023-11-30 00:12:23,295 [http-nio-80-exec-22] ppm.rest (clarity:user:session:PPM_REST_API) (1111b2e0-fd42-4fb1-9dce-fdf613aba4f2) FunctionResourceImpl :: Problem occurred while getting : workPlanDetails
ERROR 2023-11-30 00:12:23,296 [http-nio-80-exec-22] ppm.rest (clarity:user:session:PPM_REST_API) (1111b2e0-fd42-4fb1-9dce-fdf613aba4f2) 
com.niku.union.persistence.PersistenceException: 
SQL error code: 0
Error message: The index 5 is out of range.
Executed:
 with cte as (  ( select plan_id, category_id, prevtotal, base, additions, reductions,

+

ERROR 2023-11-30 20:00:53,916 [http-nio-80-exec-23] ppm.rest (clarity:user:session:PPM_REST_API) (5689d2c8-5bb1-4ce2-88fe-882aa84f9328) 
com.niku.union.persistence.PersistenceException: 
SQL error code: 512
Error message: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
Executed:
 with cte as (  ( select plan_id, category_id, prevtotal, base, additions, reductions,

 

Cause

There are apostrophes contained in the manager field, causing the issue.

Resolution

This is reported as DE78661 and is resolved in 16.2.1