All fields are read-only. IMPORTANT When this feature is released, we will change the Publish settings of ticket and task notes and attachments to Internal &Co-managed for all tickets and tasks where the Co-managed Visibility is set to Visible. Visit the Ideas forum! via the API and attached to the OnPlus Service Desk queue. This entity describes an Autotask Invoice. You cannot use the API to create items that contain Rich Text, but you can add Rich Text later via a supported method. This entity describes an Autotask Task. You cannot change a resource's ticket number prefix once created. This entity describes an Autotask Block Hour Factor, an option used with Block Hour type Contracts. An opportunity is a forecasted piece of business; an identifiable prospect that needs a product or service and offers a potential sale, project, or contract. Want to learn about upcoming enhancements? It represents any organization with which you do business. Review the setting of the Internal Only check box. Attachments are external documents that are associated with an Autotask Account, Task, Ticket, Task or Ticket Note, Time Entry, Asset, Asset Note, Project, or Opportunity entity. This entity describes an Autotask Contract. Autotask users manage Tickets through a number of modules including Service Desk, Home, CRM, and Contracts. On ticket grids, you can select the Add Note to Selected Tickets option from the bulk menu. This entity describes an Autotask SubscriptionPeriod. ChangeInfoFields are available regardless of whether they are Active or Inactive. This entity represents checklist libraries related to documents in Autotask. This object describes list items added to a check list on an Autotask ticket. A ticket can have additional assets even if there is no primary asset. https://www.autotask.com/, Press J to jump to the feed. How do I connect these two faces together? For the Autotask REST API, the Read-Only and Required field attributes have the following meanings: It is possible for a field to be both Read-Only and Required. Yep tried that - on the example given by Autotask it included "Id": "0" on the first line - but it doesn't make any difference. I know I have correctly authenticated and set the BaseURI because I can get company information for customers. The assets associated with Knowledgebase articles are recorded in this entity. 4. Making statements based on opinion; back them up with references or personal experience. This entity describes the pricing and costing tiers for a specific billing product on the Product table. Phases allow users to break projects into sub-groups of project tasks. /*]]>*/Want to tell us more? This entity contains the attachments for the TicketNotes entity. Every resource is associated with a location. The function of this entity is to describe the approval status of a project, ticket, or contract purchase cost created in Autotask. If the ticket category is associated to an SLA, then use that ID. It will not appear on the New Ticket Note or New Ticket Time Entry form. Service calls are instances of time, with specified start and stop times, that are scheduled to perform work for a Company. [CDATA[*/
This entity manages the tags associated with tickets in Autotask. This check box only appears for notes and time entries on problem tickets associated with one or more incidents. NOTE If the Ticket Note or Ticket Time Entry page is opened from the Edit Ticket page, Forward/Modify is disabled. They are also not exposed in the API or LiveReports. This entity's purpose is to describe a multi-level approval record for an Autotask time entry. We're using Power Apps to capture information and then Flow passes it to Autotask, i can pull information using GET but unable to create anything. IMPORTANT Although you can query all resources, some objects contain fields that you cannot query. This entity describes an Autotask Service added to a Recurring Service contract. Thanks for contributing an answer to Stack Overflow! This resource describes key business details for the Autotask Company 0, the Autotask user's company account. CreatorResourceID can return a ContactID. Autotask Service Bundles group multiple Services for purchase. Tracks updates to any field except changes to the LastActivityDate, LastCustomerNotificationDateTime, LastCustomerVisibleActivityDateTime. Refer to Running a global notes search. Roles are associated with a department, have a standard billing rate, and are assigned to resources for billing purposes. Tickets define service requests within the Autotask system. IMPORTANT Fields that are not visible cannot be validated. This data will not change during update operations. This entity is only used by multi-currency databases. This entity describes an Autotask Contract Block which represents a block of hours purchased for a Block Hour type Contract. This entity contains the attachments for the ExpenseReports entity. This entity's purpose is to describe a configurable alert message, associated with an account, that appears on different account-related pages. Thanks for your feedback. This entity's purpose is to describe a cost associated with an Autotask contract. The ChangeManagement module must be enabled to create a new ticket with TicketType = Change Request. You can modify the ticket category to ensure that the section is expanded when the time entry or note is first opened and that required fields are completed. Both the integration user and the API-only user must have security level permission to add or edit the entity. You can find these fields in the entity description under 'Fields that Cannot Be Queried.'. Set up the Autotask trigger, and make magic happen automatically in Microsoft Excel. If a status or quick edit field supplied by the dialog fields conflicts with an unsaved change on the Edit Ticket page, the dialogs value will be used.Information on the Insights panel will not be updated until that task or ticket is saved. Append to Resolution on # incident(s) (tickets only). Refer to Note Titles. This entity's purpose is to describe a Resource - Role - Department relationship. Assets are Products with an association to a Company entity. About note types. Billable cost items appear in Approve and Post. The allowed actions are specific to the field. This entity's purpose is to describe a Resource - Role relationship. Adding or changing a value for a recipient via the Quick Ticket Edits section will cause the names next to that check box to be added or changed accordingly. If a value is not provided for ChangeApprovalType: For the ContactID field, Contact.AccountID must = Ticket.AccountID or the ParentAccountID of Ticket.AccountID. This field is not filterable for tickets in the API. This entity describes an Autotask Opportunity. This entity describes an Autotask Ticket. /*]]>*/Want to tell us more? Changes made to the Contract by using the ContractServiceBundleAdjustment entity affect only the quantity of Contract Service units. Refer to
Scillonian Ferry In Rough Seas,
Things To Do In Binghamton This Weekend,
Difference Between Inreach And Outreach,
Articles A