The Workday REST API contains different types of entities, each of which must each be accessed separately. The performance, structure, and requirements for inserting and modifying roles varies depending on the category of the table.

Base entities

Base entities are entities that can be read directly, such as Requisitions.

Child entities

Child entities are entities that are children of other entities. For example, RequisitionsWorktags is a child entity of Requisitions. If the cmdlet needs to read RequisitionsWorktags, it must first look up Requisitions (the parent table), then extract the list of worktags.

Owned entities

Owned entities are entities that can only be read by going through another entity. For example, RequisitionRequisitionLines is owned by the Requisitions table. If the cmdlet needs to read line items from RequisitionsRequisitionLines, it must go through a specific Requisition.

Owned child entities

Owned child entities are a combination of both Owned and Child entities. For example, RequisitionsRequisitionLinesWorktags is both a child of the RequisitionsRequisitionLines table and owned by the Requisitions table. If the cmdlet needs to read RequisitionsRequisitionLinesWorktags, it must look up a specific Requisition, then look up its RequisitionsRequisitionLines, finally extracting the worktags from each line.