Changes to Attachment entities

This article explains the changes introduced to SOAP and REST Attachment entities with the release of Autotask 2021.1. It provides detail about current and future improvements, as well as links to related knowledge resources.

Index

What changed, and why?

Attachment entity changes

Previously, queries to Autotask attachment endpoints could return any attachments associated with any object and could be very inefficient across entity types.

To address this issue, we have added object ID fields to all attachment entities. Now, calls to an attachment endpoint will require the inclusion of the object you wish to query. For example, a request to the TicketAttachments entity will require a value for the ticketID field.

This improvement will enhance API performance and the granularity of the information returned to your integrations. For more information, refer to the next sections of this article.

Bug fix for Attachment entity queries

With this release, we have corrected a defect that prevented all attachments for a child entity from appearing in the parent query.

For example, tickets, ticket notes, and time entries can all have attachments, but in previous versions of Autotask, an AttachmentInfo or TicketAttachments query would return only the attachments directly attached to the ticket.

Now, the query will return all of the attachment information for the ticket, the child ticket notes, and the child time entries.

Do I need to make any changes to my integrations?

Yes. We will remove the ParentID field in an upcoming maintenance release, and it will no longer be queryable. To prevent service disruption, we recommend that you update your integrations to use the new syntax and fields. For more information about working with attachments, refer to AttachmentInfo (REST API) AttachmentInfo (SOAP API), and Working with attachments in the REST API.