Browse our Products
Aspose.Tasks for C++ 26.9 Release Notes
All Changes
| Key | Summary | Issue Type |
|---|---|---|
| TASKSNET-11196 | Optimize TimephasedData calculation: remove baseline’s TimephasedData from Task, Resource, Assignment.TimephasedData | Enhancement |
| TASKSNET-11811 | Add progress notification API when loading Project from Primavera XML format | Enhancement |
| TASKSNET-3249 | Fix calculation of summary task’s properties when non-active child task is present | Bug |
| TASKSNET-3674 | Fix overtimed assignment’s cost calculation when a resource has a non-flat rate | Bug |
| TASKSNET-11585 | Fix assignment cost timephased data generation: Resource.CostPerUse and Resource.AccrueAt should be taken into account | Bug |
| TASKSNET-11829 | Fix resource baseline reading: include items with zero work/cost but non-empty TD when reading MPP format | Bug |
Public API and Backwards Incompatible Changes
| The following public methods were added: | Description |
|---|---|
| Aspose::Tasks::Baseline::get_TimephasedData() | Gets a TimephasedDataCollection instance for this object. |
| Aspose::Tasks::Baseline::set_TimephasedData(value) | Sets a TimephasedDataCollection instance for this object. |
Related issue: TASKSNET-11196 - Optimize TimephasedData calculation: remove baseline’s TimephasedData from Task, Resource, Assignment.TimephasedData
This release optimizes timephased data calculation by no longer adding baseline timephased data to the TimephasedData collection of Task, Resource, and Assignment objects. Baseline timephased data is now stored separately within each Baseline object.
Timephased Data access changes
Before version 26.9: Baseline timephased data was stored both in the Baseline object AND in the parent entity’s TimephasedData collection. This led to increased memory consumption and performance overhead which could be noticeable for enterprise-level projects with large number of tasks, assignments and baselines.
Now:
Baseline timephased data is stored separately in Baseline.TimephasedData. The new implementation uses lazy initialization which only creates timephased data when it’s actually accessed. Regular timephased data is in the entity’s TimephasedData collection.
To retrieve baseline timephased data, use one of these methods:
For:
// Get baseline timephased data via Baseline object
auto baseline = task->get_Baselines()->GetByType(BaselineType::Baseline);
auto baselineTd = baseline->get_TimephasedData();
// Or use GetTimephasedData method
auto filteredBaselineTd = task->GetTimephasedData(start, finish, TimephasedDataType::TaskBaselineWork);
For Resource:
// Get baseline timephased data via Baseline object
auto baseline = resource->get_Baselines()->GetByType(BaselineType::Baseline);
auto baselineTd = baseline->get_TimephasedData();
// Or use GetTimephasedData method
auto filteredBaselineTd = resource->GetTimephasedData(start, finish, TimephasedDataType::ResourceBaselineWork);
For ResourceAssignment:
// Get baseline timephased data via Baseline object
auto baseline = assignment->get_Baselines()->GetByType(BaselineType::Baseline);
auto baselineTd = baseline->get_TimephasedData();
// Or use GetTimephasedData method
auto filteredBaselineTd = assignment->GetTimephasedData(start, finish, TimephasedDataType::AssignmentBaselineWork);
Migration Guide Old code example:
// Get all timephased data including baseline data
auto allTd = task->get_TimephasedData();
// Filter baseline data
auto baselineTd = allTd->GetByType(TimephasedDataType::TaskBaselineWork);
New code example:
// Get baseline timephased data directly
auto baseline = task->get_Baselines()->GetByType(BaselineType::Baseline);
auto baselineTd = baseline->get_TimephasedData();
// Or use GetTimephasedData for filtered results
auto filteredBaselineTd = task->GetTimephasedData(task->get_Start(), task->get_Finish(), TimephasedDataType::TaskBaselineWork);