'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Calculate Parent Task Completion in Power BI Without Outline Numbers
Question details
The user needs to determine task levels, identify parent tasks, and calculate completion percentages for Project for the Web data in Power BI without double-counting subtasks.
- Product
- Power BI / Project for the web
- Device & OS
- not provided
- Scenario
- Building task hierarchies and calculating accurate project completion metrics within Power BI dashboards.
- Observed behavior
- Native outline numbers from Project for the web are not imported into Power BI, making it difficult to establish proper parent-child relationships and calculate rolled-up task completion.
Before seeking a solution, ensure you have a clear mapping of your Project for the web data structure, particularly the columns defining parent-child relationships.
Consult the Power BI and Project Technical Communities
Because this issue requires building custom DAX measures to recreate hierarchies from two distinct Microsoft products, consulting experts in official communities is the most effective approach.
Since Project for the web does not natively pass outline numbers to Power BI, you must build a reliable hierarchy using Dataverse tables. This requires advanced DAX knowledge (such as utilizing PATH functions) and a deep understanding of Project's data structure.
Identify the exact Dataverse tables, parent-child relationship columns, and the specific completion calculation logic you wish to achieve.
Navigate to the official Microsoft Power BI Community forums. Create a detailed post including your data structure and clearly state that outline numbers are missing.
Simultaneously post your query in the Project technical forum, as users familiar with Project for the web's schema can provide insights on the best way to extract and relate the raw data before passing it to Power BI.
Need a simpler way to track project tasks? Try WPS Office
If complex Power BI DAX modeling is too heavy for your needs, you can easily track project progress, calculate task completion, and manage task hierarchies using spreadsheets in WPS Office. It is a free, lightweight, and highly compatible alternative to Microsoft Office that makes project management seamless.
- 1. Download and Install: Get WPS Office for free from the official website and install it on your device.
- 2. Open your Project Spreadsheet: Launch WPS Spreadsheet and either create a new task tracker or open your existing Microsoft Excel project files.
- 3. Calculate Task Progress: Use standard spreadsheet formulas like SUM or AVERAGE to quickly roll up subtask completion percentages to parent tasks.
Frequently Asked Questions
Why aren't outline numbers available in Power BI directly from Project for the web?
Project for the web relies on the Microsoft Dataverse backend. The outline numbers are often calculated dynamically in the application's user interface and are not natively stored as simple columns exposed to the standard Power BI Dataverse connector.
What DAX functions handle parent-child hierarchies in Power BI?
To reconstruct hierarchies without outline numbers, Power BI developers typically use DAX functions like PATH, PATHITEM, and PATHLENGTH. These functions look at 'Task ID' and 'Parent Task ID' columns to flatten the hierarchy for accurate calculations.
How can I prevent double-counting subtasks in my completion calculations?
You need to ensure your DAX measure filters out parent nodes when summing total work, or you must apply a weighted average logic that only aggregates leaf-level subtasks (tasks that have no children) to roll up to the parent.
