3rd-level Custom Sub Object 'Value Required' field causes 'Copy' to not work
search cancel

3rd-level Custom Sub Object 'Value Required' field causes 'Copy' to not work

book

Article ID: 265663

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Attempting to do a direct copy on a 3rd-level sub object record where there is a string field that has a Studio property 'Value Required' will cause the 'Copy' action to not work.

Steps to Reproduce: 

  1. Create a 2nd-level and 3rd-level sub objects on any master object or resource object or investment object    
  2. On the 3rd-level sub object create a new string field in studio and mark the field as 'Value Required'
  3. Make sure the objects and the attributes are API-enabled for use in Clarity
  4. Make sure the admin user has all access rights to the master and sub-objects, especially 'copy' access rights
  5. Go to the master or resource or investment and create the 2nd-level records and some 3rd-level records, filling out the required fields
  6. Now go to the 3rd-level details fly-out, right-click to copy a record   

Expected Results: To see the Name & ID fields on the modal to create the copy of the source 3rd-level record. 

Actual Results: The modal appears WITHOUT the name & ID fields and a toast message appears indicating the required value field is secured or not supported.  NOTE: the field was NOT set up for attribute level security. 

Workaround: Remove the 'Value Required' property from the Studio attribute definition and the copy actions will work, or do not use the 'Copy' action for 3rd-level records. 


For this example, I created 'SubResource' 2nd-level Object and 'SubSubResource' 3rd-level object under the 'Resource' object.

I created a string field with an API Attribute ID = r_categoryType. 

I did NOT secure the field through Clarity Administration Attributes grid. 

Environment

Release 16.1.2 

Cause

DE69829 

Resolution

Fixed in Release 16.1.3 and in Release 16.1.2 Patch #1 (16.1.2.1).