Solution ID: prim80325
Nested Calculated UDF’s increase load time of scorecards in Portfolio Analysis.
Status: Reviewed
Version(s): 6.0, 6.1, 6.2, 6.2.1

Problem: Nested Calculated UDF’s increase load time of scorecards in Portfolio Analysis.
Problem: Calculated User Defined Fields performance.
Problem: Performance with nested calculated UDF’s is slow.
Problem: Performance with multiple levels of calculated UDF’s are slow.
Problem: Example:

Overall Score is the field displayed on the scorecard.  Three separate Calculated UDF’s  (Score 1, Score 2, and Score 3) produce the Overall Score’s result. 


Then each of those Score’s has a sub score that are calculated which produces its result, i.e. Score 1.1 + 1.2 = Score 1, Score 2.1 + 2.2 = Score 2, Score 3.1 + 3.2 = Score 3



The deeper the levels means it will take more time to load.
Fix: This known problem in P6 Web is currently under review and may be corrected in a future release. 
Fix: WORKAROUND:

Reduce the levels of Calculated Fields. 


Example:


Remove Score 1.1, 1.2, 2.1, 2.2, 3.1, 3.2 and make them a manual field.