TABLE OF CONTENTS
- Schedule Core Fields
- Resource Core Fields
- Calendar Core Fields
- Activity Core Fields
- Resource Assignment Core Fields
- Successor Core Fields
- Structure Core Fields
This article applies to all three P6 connectors – P6 EPPM Web Service, P6 EPPM REST API and P6 XER File – which share the same import logic. On download each ILAP core field is written to the matching P6 field; references (Calendar, Resource, the successor Activity) are resolved on the P6 side. A blank Formula means the value is written unchanged.P6 updates the existing matched project rather than creating a new one, so the Schedule fields are written onto that project. New calendars, resources and structures are added only when the matching “Allow appending…” option is enabled; existing objects are matched and (for activities, assignments and links) updated.Activity work hours are carried on the resource assignment (Planned / Actual Units), not on the activity itself; the activity stores its durations, dates and float.P6 stores a single primary constraint per activity. When more than one constraint field is set, the first one in the order listed below is the one applied.Schedule Core Fields
| Core field name | Api field | Formula | Data type | Description |
| Description | Name | Text | The schedule's name or title. | |
| StartedDate | StartDate | Date | The date the schedule started (or is planned to start). | |
| CompletedDate | FinishDate | Date | The date the schedule finished (or is planned to finish). | |
| CutoffDate | DataDate | Date | The data date / status date the schedule is current as of. | |
| Code | Id | Identifies the P6 project to update (matched, not overwritten) | Text | The schedule's unique identifier in the host system. |
Resource Core Fields
| Core field name | Api field | Formula | Data type | Description |
| Description | Name | Text | The resource's name or title. | |
| Code | Id | Existing resources are matched by reference; a new resource gets a generated P6 Id (the Code itself is not written) | Text | The resource's unique identifier in the host system. |
Calendar Core Fields
| Core field name | Api field | Formula | Data type | Description |
| Description | Name | New calendars only; a numeric suffix is added if the name already exists. The standard work week and holidays are rebuilt from the calendar's working-time periods. | Text | The calendar's name or title. |
| Code | (matched) | Identifies the P6 calendar to reuse | Text | The calendar's unique identifier in the host system. |
Activity Core Fields
| Core field name | Api field | Formula | Data type | Description |
| ActivityType | Type | Map: RegularActivity → Task Dependent, MilestoneStart → Start Milestone, MilestoneFinish → Finish Milestone, Hammock → Level of Effort | Enum | The kind of activity. Possible values: RegularActivity, MilestoneStart, MilestoneFinish, Hammock. |
| Description | Name | Truncated to 120 characters | Text | The activity's name or title. |
| EarlyStart | EarlyStartDate | Also the default for PlannedStartDate when that is not mapped | Date | The earliest the activity can start (forward-pass schedule date). |
| EarlyFinish | EarlyFinishDate | Also the default for PlannedFinishDate when that is not mapped | Date | The earliest the activity can finish (forward-pass schedule date). |
| LateStart | LateStartDate | Date | The latest the activity can start without delaying the project (backward pass). | |
| LateFinish | LateFinishDate | Date | The latest the activity can finish without delaying the project (backward pass). | |
| ActualStart | ActualStartDate | Date | The date the activity actually started. | |
| ActualFinish | ActualFinishDate | When set, PercentComplete is left unspecified | Date | The date the activity actually finished. |
| CurrentProgress | PercentComplete | PercentComplete = CurrentProgress / 100 | Number | The activity's progress, as a percentage. |
| DurationHours | PlannedDuration | Number | The activity's duration in hours. | |
| RemainingDurationHours | RemainingDuration | Number | The activity's remaining duration in hours. | |
| FreeFloatHours | FreeFloat | Number | Hours the activity can slip without delaying any successor. | |
| TotalFloatHours | TotalFloat | Number | Hours the activity can slip without delaying the project finish. | |
| MustStartOn | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Start On | Date | Constraint date: the activity must start exactly on this date. |
| MustFinishOn | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Finish On | Date | Constraint date: the activity must finish exactly on this date. |
| StartNoEarlierThan | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Start On or After | Date | Constraint date: the activity must start on or after this date. |
| StartNoLaterThan | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Start On or Before | Date | Constraint date: the activity must start on or before this date. |
| FinishNoLaterThan | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Finish On or Before | Date | Constraint date: the activity must finish on or before this date. |
| FinishOnOrAfter | PrimaryConstraintDate PrimaryConstraintType | Sets the primary constraint type to Finish On or After | Date | Constraint date: the activity must finish on or after this date. |
| StartAsLateAsPossible | PrimaryConstraintType | Sets the primary constraint type to As Late As Possible (no date) | Boolean | Constraint: the activity should start as late as the schedule allows. |
| Calendar | CalendarObjectId CalendarName | Matched to the imported P6 calendar; falls back to the project default / 24-hour calendar | Reference | The calendar that governs the activity's working time. |
| Code | Id | Truncated to the project's maximum activity-id length | Text | The activity's unique identifier in the host system. |
Resource Assignment Core Fields
| Core field name | Api field | Formula | Data type | Description |
| PlannedHours | PlannedUnits | Number | Planned work hours assigned to the resource on the activity. | |
| ActualHours | ActualUnits | Number | Actual work hours the resource has spent on the activity. | |
| CurrentProgress | UnitsPercentComplete | UnitsPercentComplete = CurrentProgress / 100 | Number | The progress of the resource's assignment, as a percentage. |
| LagHours | PlannedLag | Number | The lag, in hours, applied to the assignment. | |
| DurationHours | PlannedDuration | Taken from the parent activity's planned duration (P6 assignments have no separate duration) | Number | Duration in hours of the resource's assignment. |
| Resource | ResourceObjectId | Matched to the imported P6 resource | Reference | The resource assigned to the activity. |
Successor Core Fields
| Core field name | Api field | Formula | Data type | Description |
| Type | Type | Map: StartToStart → Start to Start, StartToFinish → Start to Finish, FinishToStart → Finish to Start, FinishToFinish → Finish to Finish | Enum | The dependency relationship type. Possible values: StartToStart, StartToFinish, FinishToStart, FinishToFinish. |
| LagHours | Lag | When “Adjust lags” is enabled, Lag = LagHours x (destination calendar hours-per-week / link calendar hours-per-week); otherwise the hours are written unchanged | Number | The lag, in hours, on the relationship. |
| SuccessorObject | SuccessorActivityObjectId | The successor activity (the link target); the predecessor is the activity the link belongs to | Reference | The successor activity (the link target). |
Structure Core Fields
| Core field name | Api field | Formula | Data type | Description |
| Type | (structure kind) | Wbs is written as a P6 WBS; FlatList / HierarchicalList as a P6 activity code type; other types are skipped | Enum | The kind of structure. Possible values: Wbs, FlatList, HierarchicalList. |
| Description | ActivityCodeType.Name | Used as the P6 activity code type name (list structures only) | Text | The structure's name or title. |
| Code | WBS.Code / ActivityCode.CodeValue | Each element's Code becomes the WBS node code (named “{Code} - {Description}”) or the activity code value; its Description becomes the node name / code description | Text | The code of each structure element (WBS node or activity code value) written to P6. |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article