search cancel

MUX error while replacing a resource with a role


Article ID: 203480


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


STAFF Module Replace Person with a new instance of a Role that is already on the team cannot deal with a custom field. 

Multiple instances of the same Role can be booked on an investment.  

Modern User Experience (UX) has the new ability to replace a person with a Role, thereby adding a new instance of a Role on the team. 

If the Team Object has any custom attributes, performing this action causes the application to generate an error and the action is not successful. 

It does not matter if the field is enabled for API or not and it does not matter if the field is not required. 

If there are not already any instances of that Role on the Staff, then it is successful. 


  1. Log in to Clarity, Administration, Studio: Objects 
  2. Go to the Team Object and create at least 1 user-defined attribute (attribute1) 
  3. Go to the Modern UX, any investment, STAFF Module 
  4. Add 'Ives, Blair (DBA)' to the team 
  5. Double-click in the pull-down field for 'Ives, Blair (blairIves)' and replace with the 'DBA (csk.dba)' role (works as expected) 
  6. Add 'Carmen, Ed (DBA)' to the team 
  7. Double-click in the pull-down field for 'Carmen, Ed (edcarmen)' and replace with the 'DBA (csk.dba)' role 

Expected Results: For the person to be replaced with the DBA role, in effect adding a new instance of that role. 

Actual Results: The action is not successful and the attribute ID (attribute1) is shown in the toast message. 



Clarity Release: 15.8.1, 15.9, 15.9.1


The issue was reported as product defect (Defect ID - DE58702)


Fixed in 15.9.2

Workaround: None