TaskSecondaryResources

This entity describes a secondary resource assigned to a project Task. Secondary resources are different from the primary resource. A Task can have more than one Secondary Resource assigned, and a task can have secondary resources without a primary resource assigned.

NOTE  You can refer to the Online Help to find root and child access URLs of the entity you wish to query. Refer to Finding resource and child access URLs of REST API entities for more information.

Entity details

Entity Name: TaskSecondaryResources

Entity Path:

/atservicesrest/v1.0/TaskSecondaryResources

Parent Entity:

Tasks

Can Create:
Can Update:  
Can Query:
Can Delete:
Can Have UDFs:  

Conditions and requirements

General

  • A task may have up to a maximum of 50 secondary resources.
  • 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.
  • The secondary resource cannot be the primary resource on the task
    (taskSecondaryResource.Resource ID cannot equal task.assignedResourceID).
  • resourceID and roleID must be an existing Resource/Role pair in Autotask.
  • Resources without security level access to projects have RESTRICTED access to Tasks; that is, they must be assigned to the task to add and remove secondary resources for the task.
  • Secondary resources on 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 fields for this entity. Refer to the following articles for more information about working with these fields:

To learn how to query picklist endpoints, refer to Understanding picklists.

Notes

  • For string datatypes, the number in parentheses ( ) indicates the maximum number of characters allowed.
  • LT indicates Local Term.
  • If this entity has child collections, they will appear in a Child collection access URLs or an Entity URLs and relationships drop-down in the Entity details section of this article.
  • You can call the /query/count/ endpoint of a resource to determine how many records a collection holds.
Field Name Datatype Read-Only Is Required Reference Name Picklist
id long    
resourceID long   Resources  
roleID long   Roles  
taskID long   Tasks  

Additional resources