CMN-0009: Attribute 'Booking Status' has invalid Lookup Value '10'
search cancel

CMN-0009: Attribute 'Booking Status' has invalid Lookup Value '10'

book

Article ID: 370436

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Selecting Mixed booking in booking status attribute generates an error  

Steps to Reproduce: 

  1. Login to Clarity with Administrative privilege's
  2. Navigate to Classic Clarity --> Administration --> Project Management --> Settings and Check Allow Mixed Booking    
  3. Logout and Login back to MUX --> Project --> Pick a project and inside the project instance navigate to Staff Module  
  4. Add few staff and have Booking Status attribute in the grid 
  5. Now try changing the Booking Status to Mixed from the drop down 

Expected Results: Since Booking Status is driven by updating Allocations and Hard Allocations in the PER-PERIOD METRICS, Mixed booking either shouldn't be shown as in Classic Clarity Mixed booking is not shown under team

Actual Results: Mixed booking is driven by updating Allocations and Hard Allocations in the PER-PERIOD METRICS drop-down list and status automatically changes, however user can change manually and it generates an error "CMN-0009: Attribute 'Booking Status' has invalid Lookup Value '10'". 

Sample Error logs 

ERROR 2024-06-19 04:06:20,754 [http-nio-8080-exec-269] rest.validation (clarity:XXXX:7259489__9CA4CCF7-49DF-4123-832F-E15E09A2A9C4:PPM_REST_API) (d4d96614-8ff9-42dc-909e-43aedb2413ca) ExceptionInfo ::  Could not update resource. Resource name: obaStaffs. Error code: validation.lookupValueInvalid Error message: CMN-0009: Attribute 'Booking Status' has invalid Lookup Value '10'

Environment

Clarity 16.1.x, 16.2.x

Cause

DE94825

Resolution

DE94825 is fixed in 16.3.0 (Targeted to release November 2024) and also backported to 16.2.3 patch 1 

Mixed booking is system driven and user shouldn't manually change. Details can be found in documentation