TicketSecondaryResources

This entity describes a secondary resource assigned to a Ticket. Secondary resources are different from the primary resource. A Ticket can have more than one Secondary Resource assigned, and 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: TicketSecondaryResources

Entity Path:

/atservicesrest/v1.0/TicketSecondaryResources
Parent Entity: Tickets
Can Create:
Can Update:  
Can Query:
Can Delete:
Can Have UDFs:  

Conditions and requirements

  • A ticket may have up to a maximum of 50 secondary resources.
  • The secondary resource cannot be the primary resource on the ticket
    (ticketSecondaryResource.Resource ID cannot equal ticket.assignedResourceID).
  • resourceID and roleID must be an existing Resource/Role pair in Autotask.

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  
ticketID long   Tickets  

Additional resources