Non-current baseline data not in slice table
search cancel

Non-current baseline data not in slice table

book

Article ID: 382762

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Non-Current Baselines do not get sliced when you create a custom slice for Non-Current Baseline Assignment Usage, Non-Current Baseline Team Usage ...

STEPS TO REPRODUCE:

1. Create a project that spans for a week
2. Add a team member.
   Create a task and assign the team member. Add some ETC
3. Create a project baseline:
   My Current baseline: Notice you have some baseline values coming from the team/assignment
4. Create a second baseline and do not set it as current
5. Now you have two baselines: one current and one non-current
6. Administration > Data Administration > Time Slices
7. Create a new slice
   Name Non-current assignment baseline
   Rollover Interval: Yearly
   From date 01/01/2024
   Slice Period: Monthly
   Periods: 12
   Item: Non-Current Baseline Assignment Usage
8. Take note of the slice ID: example 5020002
9. Ensure the time slicing job runs
10. Check the slice at DB side:
    select * from prj_blb_slices where slice_request_id = 5020002

Expected Results: Non-current baseline data to be present at the slice table
Actual Results: The slice table does not contain non-current baseline data

Cause

This was analyzed through DE156579

Resolution

This has been determined to be the current design. Only 'Current' baseline data is sliced.

It will require an enhancement to change the current functionality. Please log an idea to request a functionality change.

Workaround: Go to the Project Baseline page and change the non-current baseline to be the current revision. Then change the now non-current baseline to be the current revision again. Check the tables again and you will see the current and non-current baselines have been sliced.