ResourceRoleDepartments

This entity describes a Resource - Role - Department relationship. A resource must be assigned to at least one role. Resources are assigned to one or more roles through their department. They can also be assigned service desk roles. This entity describes Resource's Role and Department associations.

A role is required when a resource is assigned to a ticket or task. The role rate dictates the base rate for work the resource performs on that task or ticket.

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

Entity Path:

/atservicesrest/v1.0/ResourceRoleDepartments

Parent Entity:

Resources

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

Conditions and requirements

  • resourceID cannot be changed on update. No error is returned; the new value is ignored.
  • A Resource must have a default Role and Department. If ResourceRoleDepartment.isDefault = True, on update the value cannot be set to False.
  • On create or update, ResourceRoleDepartment.isDefault can be set to True. If ResourceRoleDepartment.isDefault = True already exists, the current instance is set to False and the new instance becomes the Default.
  • ResourceRoleDepartment cannot be created with an inactive roleID, resourceID, or departmentID, but update is allowed. You cannot update resourceID, roleID, or departmentID with an inactive item.

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
departmentID integer   Departments  
id long    
isActive boolean      
isDefault boolean      
isDepartmentLead boolean      
resourceID integer Resources  
roleID integer   Roles  

Additional resources