OWB: save project gives error: Unable to save project NIKU\XXXXX. Referenced record does not exist in the database.

book

Article ID: 52389

calendar_today

Updated On:

Products

CA Identity Governance CA Identity Portal Clarity PPM On Premise

Issue/Introduction

Description:

OWB: Save project to Clarity gives error: Unable to save project NIKU\XXXXX. Referenced record does not exist in the database. This happens when a role is on the project multiple times and you change the assignment or project role to a different instance of the role.

STR 1:

  1. Create a project in Clarity and add a role twice to the project.
    Note: you have Role and Role-2

  2. Open the project in OWB

  3. Assign the first instance of the role to a task - Role

  4. Create a view with task, resource and assignment role fields

  5. Change the assignment role value to the second instance of the - Role-2

  6. Save the project to Clarity

STR 2:

  1. Create a project in Clarity and add a role twice to the project.
    Note: you have Role and Role-2

  2. Open the project in OWB

  3. Modify the first instance of the role

  4. Click on the Advanced tab

  5. Change the Project Role field to the second instance of the role

  6. Save the project to Clarity

Expected Results: Not able to select the second instance of the role in the assignment role field or project role field.
Actual Results: You are allowed to select the second instance of the role and on saving to Clarity you get: Unable to save project NIKU\XXXX. Referenced record does not exist in the database.

 

Environment

Release:
Component: PROJECTS

Resolution

Workaround:
STR 1: Do not change the Assignment Role field to a second instance of the role.
STR 2: Do not change the roles Project Role to the second instance of the role.