Data fetched for all custom attributes in Project Properties load - Modern UX
search cancel

Data fetched for all custom attributes in Project Properties load - Modern UX

book

Article ID: 371837

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Steps to Reproduce:

  1. Create one attribute each of all the possible data types in the Project object. There will be 15 attributes in total. Populate 'Attribute Alias ID' against all of them
  2. Create a Blueprint. Edit the Blueprint to remove all modules except 'Properties', 'Task' and 'Staff'. Remove all sections except 'Project Summary', in the 'Properties' tab. Remove all fields except 'Project Name' and 'Project ID' in the 'Project Summary' tab
  3. Create a Project, and associate it with the Blueprint from above
  4. Enable trace on the user being used from Classic UI -> Administration -> Resources. Use 'Trace Statements' option
  5. Logout and Login
  6. Open the Project created in step 3
  7. Obtain the app-trace.xml from security.logs page
  8. Search the file with the 'API Alias ID' of any attribute created in step 1. This will show a SQL that fetches data when a Project instance is loaded

Expected Results: This SQL only fetches data that is relevant for displaying within a Project

Actual Results: It fetches data for all custom attributes defined within Project, that have an 'API Alias ID'.

Environment

Latest version tested: 16.2.2.

Cause

DE116126

Resolution

DE116126 is under review.