Project Count Varies When Using A Manual Aggregation Of Project ID Dimension Instead Of Using The "# Of Projects" Fact Column Within A New Analysis From "Primavera - Project History" Subject Area (Doc ID 2389797.1)

Last updated on APRIL 24, 2018

Applies to:

Symptoms

ACTUAL BEHAVIOR
When creating an initial analysis from the Project History subject area to display a count of project IDs (using a manual count aggregation of the General - (Project) > Project Id column) (with/without additional columns added to the analysis initially), modifying the analysis and adding additional column(s) cause the manual aggregation count of a dimension to differ from the original values.

For example:

• If displaying only a count(project id) in the analysis, adding the EPS Root ID to the list can result in count(project ID) value to differ from the original count.
• See steps below for complete detail of the different use cases

EXPECTED BEHAVIOR
When creating an initial analysis from the Project History subject area to display a count of project IDs (using a manual count aggregation of the General - (Project) > Project Id column) (with our without additional columns added), modifying the analysis and adding additional column should not result in the value to the manual aggregation to differ from the original display.

STEPS TO REPRODUCE
Example Analysis 1:

• Using Primavera - Project History
• Columns:
  
  • General - (Project) > COUNT(ProjectID)
  • EPS > EPS ID (Root Level)
  • Note: The count column is a formula created by customer.
• Results:
  
  • Count(Project ID): 89
  • EPS ID (Root Level): EPS_Example

Example Analysis 2:

• Using Primavera - Project History
• Columns:
  
  • General - (Project) > COUNT(ProjectID)
  • Note:  The count column is a formula created by customer.
• Results:
  
  • Count(Project ID): 117

Note the discrepancy between the two analysis project ID counts when simply adding a root EPS level column that should not change the project ID count value. 

Changes

Cause