TicketAdditionalConfigurationItems

This entity describes one or more Autotask Assets (previously known as Configuration Items) assigned to a Ticket beyond the primary asset(ticket.configurationItemID). Assets are products that are associated with a Company entity. Autotask users manage assets through the CRM Module (CRM > Assets, or CRM > Companies > Assets tab). A ticket can have additional assets even if there is no primary asset.

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: TicketAdditionalConfigurationItems

Entity Path:

/atservicesrest/v1.0/TicketAdditionalConfigurationItems

Parent Entity:

Tickets

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

Conditions and requirements

  • A ticket can have no more than 100 additional assets.
  • A Ticket can have additional assets without having a primary asset.
  • You cannot create an additional asset for an configurationItemID that is the primary asset on the ticket (Ticket.configurationItemID). The additional asset will be removed from the list.
  • You cannot create duplicate additional assets (same ticketID and configurationItemID).
  • You cannot create additional assets if the configurationItemID does not belong to the same account as the ticket.
  • You cannot create additional assets if the configurationItemID is inactive or does not exist.

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
configurationItemID integer   ConfigurationItems  
id long    
ticketID integer   Tickets  

Additional resources