Others

How to Fix Project Server Timephased Work Discrepancies in Power BI

Tauseeq Magsi Sep 30, 2026 868 views

Question details

The user needs to troubleshoot and resolve differences between the remaining work data recorded in Project Server and the future phased work displayed in the Power BI AssignmentTimephasedDataset.

How to Fix Project Server Timephased Work Discrepancies in Power BI

Product: Project Server / Power BI
Device & OS: not provided
Scenario: Analyzing project resource allocation and remaining work using Power BI connected to Project Server OData feeds.
Observed behavior: Future phased work data in Power BI does not match the actual remaining work recorded in Project Server.

Before you start

Ensure you have the latest data refresh completed in Power BI and verify your access permissions to the Project Server OData feeds.

Solution 1Recommended

Verify Power Query Extraction and Transformations

Check the Power Query steps to ensure timephased data isn't being inadvertently filtered out or transformed incorrectly during the import process.

Often, discrepancies arise because Power Query filters out future dates or incomplete records during the data transformation phase. Reviewing the applied steps can identify where the missing data is being dropped.

Open Power Query Editor

In Power BI Desktop, click on 'Transform Data' on the Home tab to open the Power Query Editor.

Check Date Range Filters

Select the AssignmentTimephasedDataset query and review the 'Filtered Rows' steps in the Applied Steps pane. Ensure no date filters are accidentally excluding future periods where remaining work is scheduled.

Review Aggregations

Examine any 'Group By' or aggregation steps. Confirm that the 'Remaining Work' or 'Timephased Work' columns are being summed correctly without dropping future records.

Verify Power Query Extraction and Transformations

OData Feed Limitations: Large datasets from Project Server might hit OData feed limits or timeout. Ensure the entire dataset is being extracted by checking your refresh logs.

Solution 2

Validate Data Mapping and Relationships

Ensure the relationships between the Tasks, Assignments, and Timephased datasets are correctly established in your Power BI model.

Free Microsoft Office alternative

Analyze Exported Project Data Easily with WPS Office

While Project Server and Power BI handle complex enterprise datasets, WPS Spreadsheet offers a lightweight, fast, and free alternative for analyzing exported project data, creating quick pivot tables, and sharing reports without compatibility issues.

1. Export Data: Export your project task and resource data from Project Server to a .xlsx file.
2. Open in WPS Spreadsheet: Launch WPS Spreadsheet and open the exported file seamlessly.
3. Analyze Data: Use built-in Pivot Tables and charts to analyze remaining work without complex OData connections.

Free, lightweight, and fast alternative to Microsoft OfficeFully compatible with Microsoft Excel (.xlsx) files exported from ProjectFamiliar user interface for easy pivot table and chart creationBuilt-in templates for project management and timeline tracking

Frequently Asked Questions

Why is future timephased work missing in Power BI?

Future timephased work often goes missing due to date filters applied in Power Query or the OData feed extraction, which might inadvertently exclude records scheduled past the current date or project status date.

How does AssignmentTimephasedDataset differ from task remaining work?

Task remaining work is a single aggregated total of the hours left on a task, whereas the AssignmentTimephasedDataset breaks down those remaining hours into specific time periods (e.g., daily, weekly) for each resource assignment.

Can incorrect status updates cause timephased data discrepancies?

Yes, if timesheets or task statuses are not properly approved and published in Project Server, the timephased data in the OData feed will not reflect the latest actuals and remaining work.

Office Quick Solutions