Unable to Update Department in Resource Workspace Without a Location in Common
search cancel

Unable to Update Department in Resource Workspace Without a Location in Common

book

Article ID: 450618

calendar_today

Updated On:

Products

Clarity FedRAMP Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

It is not possible to change the Department in the Resource workspace unless the two Departments have a Location in common.

Steps to Reproduce:

  1. Create a Department OBS structure that has two Departments, 'Business Operations' and 'Development'.
  2. Associate two different Locations to each department.
    For example:
    Business Operations: Sydney (but NOT Tokyo)
    Development: Tokyo (but NOT Sydney)
  3. In Classic (Home > Resource Management > Resources > [resource] > Properties > Financial) and activate financially and set its Department to "Business Operations" and Location to "Tokyo".
  4. Add an API alias to the Resource object Department OBS attribute.
  5. Navigate to the Modern UX Resource workspage and add the columns: Department, Location, Department OBS.
  6. Try to change the Department and Location for that resource from Business Operations/Sydney to Development/Tokyo.

Expected Results: You can change Department and Location to Development/Tokyo.

Actual Results:

  • Using Department OBS attribute (try to change to Development): Department OBS value reverts back to Business Operations.
  • Using Location (try to change to Tokyo): Tokyo is not listed, as it is not a valid Location for Development Department.
  • Using Department (try to change to Development): A Conditional Required Modal appears, but Location only lists Sydney (current value - not the location for the new department).

Environment

Clarity 16.4.2

Cause

DE210014

Resolution

This issue is under review.

Workaround: Use Classic to update Department, which will blank Location that need to be set to the right Location before saving (both Department and Location changes will be saved at the same time).