search cancel

Clarity: Orphan team data can be left behind in internal slice tables


Article ID: 50630


Updated On:


Clarity PPM SaaS Clarity PPM On Premise



Orphan team data can be left behind in internal slice tables.

Steps to Reproduce:

  1. Login to Clarity as an administrator user

  2. Main Application > Projects > Team

    Add a labor resource to the project team
    Assign the resource to the Project Effort Task
    ** Make a note of the Project Internal Id (i.e. 5000000)

  3. Project > Properties > Baseline

    Create a current baseline for the project

  4. Execute the 'Time Slicing' job

  5. Copy the attached Query

    Modify the Query to replace <projectid> with the Project Internal Id (i.e. 5000000)
    Execute the Query in a database query tool and examine the results

  6. Main Application > Projects > Team

    Select and delete the labor resource added in Step #1

  7. Execute the Query in Step #5 again

Expected Result: No rows returned from query

Actual Result: Rows are returned. (Orphan data in PRJ_BLB_SLICES_D_ALC, PRJ_BLB_SLICES_W_ALC, PRJ_BLB_SLICES_M_ALC and more)

This issue affects all PRJ_BLB_SLICE tables for data related to the use-case described.


Contact CA Support for assistance in deleting the orphaned records.

This issue has been documented and is assigned to development for review. If you are experiencing this problem and the workaround above does not significantly help, please contact CA Clarity Support.

Keywords: CLARITYKB, CLRT-22755, CLRT-8046, CLRT-22846, clarity12open.


Release: ESPCLA99000-12.1-Clarity-Extended Support Plus

Attachments get_app