"Required fields: You do not have the correct permissons to view these attributes"

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

"Required fields: You do not have the correct permissons to view these attributes" toast message appears when editing a parameterized lookup in the grid if the following conditions are met:

• The related lookup field is required
• The related lookup field is secured and you do not have access to it and
• The "Clear parameterized lookup values when a source attribute changes" feature toggle is on

STEPS TO REPRODUCE: 

1. Go to Classic PPM > Studio > Objects > Project object
2. Make the OOTB Project Category and Project Type attributes required. Check the value Required option
3. Go to MUX and add the Project Category and Project Type attributes to the grid view
4. Under MUX > Administration > Attributes > locate the Project Category attribute
5. Make it secure and do not add any group to Access Edit or Access View fields.
6. On the project grid, notice that the Project Category field is not displayed because the user does not have access to it as it is secured
7. Change the value of the Project Type attribute
8. Changes are saved
9. In MUX > Administration > Feature Toggles > Enable the "Clear parameterized lookup values when a source attribute changes"
10. As on step 7, change again the Project Type attribute value

Expected Results: Changes to be saved
Actual Results: You get the following error: Required fields: You do not have the correct permissons to view these attributes

Environment

Clarity 16.3.0

Cause

This was analyzed through DE165926 and determined to be the desired design.

In Clarity 16.3.0, we made an enhancement to parameterized lookup where if you change the source fields of a parameterized lookup, it would clear parameterized lookup value if it is an invalid source/parameterized lookup combination. (Documentation).

We did this to match Classic. In Classic, we did this to ensure data integrity to make sure the parameterized lookup value matches a correct source attribute value. When we implemented parameterized lookups in MUX, we didn't clear out the parameterized lookup value when there was an invalid source/parameterized lookup combo which caused data corruption.

Resolution

If you are allowing end-users to change the project type (source attribute) you need to show the corresponding parameterized lookups to ensure there is a valid source/parameterized lookup combo.  

Other possible approaches: 

• Disable the "Clear parameterized lookup values when a source attribute changes" feature toggle OR
• Do not make the attribute required OR
• Unsecure the field