Project Structure | Troubleshooting
The following diagram illustrates how Projects and corresponding tasks are related.
- Each node is related to its child node through the parent column
- All nodes should have the same top_task column value which should be the sys_id of the Top project
Project data integrity
In any project, the following conditions should be met
- The top_task column of all nodes (including the Top Project) should be populated with the sys_id of the Top project
- All records, except the Top Project, should have the parent column populated
- The parents in the structure should be under the same Top Project - they should not belong to a different project structure
Viewing the entire project structure
- In he Application Navigator, type planned_task_list.do in the Filter navigator field and press enter or return on your keyboard.
- To list all records in the project structure, run the following query:
[Top task] [is] [<top_project_sys_id>]
The relationship between two nodes is specified through the planned_task_rel_planned_rel table.
The relationship types are:
- Finish to Start (successor planned start date is derived from predecessor planned end date)
- Start to Start (successor planned start date is derived from predecessor planned start date)
- Finish to Finish (successor planned end date is derived from predecessor planned end date)
- Start to Finish (predecessor planned start date is derived from successor planned end date)
Identifying relations in a project
Use one of the following to see the sys IDs of relation records:
- update set attached to KB article Project Management Diagnosis Tool
- the Planning Console
- the following script:
Copy the records and query the planned_task_rel_planned_task table for the sys IDs.