Relationships & Logic
Predecessors in Project / MSPDI vs P6 TASKPRED
FS/SS/FF/SF + lag in Project / MSPDI vs TASKPRED
Project / MSPDI
Task/PredecessorLink:
| Child | Microsoft |
|---|---|
| PredecessorUID | predecessor task unique ID |
| Type | 0=FF, 1=FS, 2=SF, 3=SS |
| LinkLag | lag in tenths of a minute |
| LagFormat | display unit (3=m … 7=d … 9=w …; see Microsoft LagFormat list) |
| CrossProject / CrossProjectName | external predecessor |
Microsoft Type integers (PredecessorLink):
| MSPDI | Meaning |
|---|---|
| 0 | Finish-to-Finish |
| 1 | Finish-to-Start |
| 2 | Start-to-Finish |
| 3 | Start-to-Start |
Default in the UI is FS. SF exists in the schema; do not claim a given file has SF unless that file was read.
Contrast with P6 TASKPRED
| P6 | Project | |
|---|---|---|
| Row | TASKPRED | PredecessorLink on the successor task |
| Successor | task_id | the parent Task |
| Predecessor | pred_task_id | PredecessorUID |
| Type storage | pred_type strings (MPXJ: PR_FS / PR_SS / PR_FF / PR_SF; Oracle map does not list codes) | integer 1 / 3 / 0 / 2 |
| Lag | lag_hr_cnt hours | LinkLag tenths of a minute |
| Lag calendar | schedule option (pred / succ / 24h / project default) | unverified here — Microsoft pages fetched do not name a lag calendar option |
| Comments | comments | no cited PredecessorLink comment field |
Hours → tenths-of-a-minute is a unit conversion, not a behavior change. Which calendar burns the lag can change dates after a round-trip. See p6/lag-calendar.md and p6/taskpred.md.