ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity: Why baseline fields in PRASSIGNMENT table are not always updated?

book

Article ID: 53380

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Description:

Question: Why baseline fields in PRASSIGNMENT table are not always updated?
Answer: Baseline fields in the assignment and task tables are deprecated. Use the PRJ_BASELINE_DETAILS table for these values.

Solution:

All baseline values that are outside of the PRJ_BASELINE_DETAILS table are considered deprecated and are not kept up to date by Clarity. This includes any fields that start with prbase in prassignment, prtask and any of the investment tables.

Example:

  • Deprecated query

    select prbasesum/3600/8 baseline from prassignment
    where prtaskid = xxxx -- internal id of the task;

  • Current method to obtain baseline information via SQL Query

    select sum(b.usage_sum)/3600/8 baseline
    from prj_baseline_details b
    where b.object_type='TASK'
    and b.is_current = 1
    and b.object_id = xxxx -- internal id of the task;

Please consult the technical reference guide for more information.

Keywords: CLARITYKB, attributes, projects, tasks, assignments, resources.

Environment

Release: NCSVCS05900-8.1-Clarity-Service Connect-for MS-SQL
Component: