TaskPredecessor
IMPORTANT The SOAP API entered a limited enhancement phase in Q4 2020. Access to version 1.6 will eventually be deactivated. At this time, there is no end-of-lifecycle date.
This entity describes a predecessor/successor arrangement between two project schedule items. A predecessor item comes before one or more tasks (successor tasks) in the Project schedule. A successor task is scheduled to begin at the predecessor task's end date plus the number of "lag" days specified. for the predecessor.
Entity details
You can also retrieve this information with the Web Services API call The getEntityInfo() SOAP API call.
Entity Name: | TaskPredecessor |
Can Create: | |
Can Update: |
Lag days only |
Can Query: | |
Can Delete: | |
Can Have UDFs: |
Conditions and requirements
General
- If Autotask receives a create, update, or delete request for this entity and its corresponding module is unavailable, the API will return the error message, "The logged in Resource does not have the adequate permissions to update this entity type." For more information about installed modules, refer to our Modules article.
- Currently, the API does not support project Phases as predecessors.
- Only LagDays can be updated.
- The start date of the Successor Task (SuccessorTaskID) will shift based on the Predecessor Task's (PredecessorTaskID) end date plus the number of Lag Days (LagDays) where specified.
- The Predecessor Task and Successor Task must be associated with the same Project.
- API user can only create(), update(), delete(), and query() TaskPredecessor for Tasks allowed by user's security level permissions, including RESTRICTED access to Tasks for users who are assigned to a Task but have no access to Projects.
- Predecessor and Successor Tasks associated with projects of Type = Baseline are read-only and cannot be created, updated or deleted via the API.
Field definitions
The following table describes the standard Autotask field objects for this entity.
- To retrieve more detailed information specific to a particular Autotask implementation, use the Web Services API call The getFieldInfo() SOAP API call.
- For information on entity UDFs, use getUDFInfo().
- For String datatypes, the number in parentheses ( ) indicates the maximum number of characters allowed.
- LT indicates Local Term.
For more information about fields marked as picklists, review our Understanding picklists article.
Field Name | Label | Datatype | Read Only | Is Required | Reference Name | Picklist |
---|---|---|---|---|---|---|
id | Task Predecessor ID | long | ||||
LagDays | Lag Days | integer | ||||
PredecessorTaskID | Predecessor Task ID | integer | Task | |||
SuccessorTaskID | Successor Task ID | integer | Task |