Whenever TaskID from PMRevenueBudget is included (either in the join to PMProformaLine or referenced in grouping), the report intermittently fails with one or both of these exceptions:
If I remove TaskID from the relationship or from the grouping, the exceptions go away but then I can’t bucket by 001/002/EXTRAS (My first segment of my task 001-000-00 etc.) and lines don’t reconcile correctly.
-
Is there any known limitation in Report Designer that prevents using
PMRevenueBudget.TaskIDin a dataset that also includesPMProformaLine/PMProformaProgressLine, even with explicit key joins? -
Is there a supported bridge I should be using instead of joining
PMRevenueBudget → PMProformaLineon(ProjectID, TaskID, AccountGroupID)? (e.g., a projection or a different DAC that exposes the budget/pro forma mapping without triggeringGetBudgetLineKey?) -
Has anyone shipped an AIA-style report that lists budget lines and pulls pro forma progress per line? If so, could you share the exact Schema Builder relationships that worked?
-
If the answer is “don’t mix these DACs in one query,” is the recommended pattern to:
-
base the report on
PMRevenueBudgetonly and use subreports to pull progress by(ProjectID, TaskID, AccountGroupID)filtered by currentRefNbr? -
or build a GI/projection that pre-flattens the mapping?
-
-
Any graph extensions or attributes on these DACs in 25.101 that would cause the query engine to inject
GetBudgetLineKey/GetProformaLineKeydespite explicit joins?