MUX - After upgrading to 16.4.1 we are not able to see custom attribute in MUX.
search cancel

MUX - After upgrading to 16.4.1 we are not able to see custom attribute in MUX.

book

Article ID: 440114

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

After upgrading to 16.4.1 users not able to see field in their projects that they used to be able to see in our previous version.

1. Create a custom attribute on the Financials object in Studio.

2. Put that attribute on the Project properties blueprint.

3. Secure attribute created in Step 1 only on the Financial object do not secure it at the Project object.

4. Log in as a user whose Group was not given View or Edit access at the Financial object and this user can't see the attribute although they have all project-related rights.

Environment

Clarity 16.4.x

Resolution

The Financial object is an abstract, like the Investment object so it applies to all of its concrete objects. If you secure the attribute on the abstract object, it hides that attribute from all of its concrete objects. If you only want it secure on Projects, you should secure it only on Project object.