EntityType: TaskBaseline (ProjectData service)

In this article
Definition
Parent element
Child elements

Contains the properties that define the reporting data for a project in the ProjectData service.

Example

The following REST query uses the TaskBaselines entity set and the BaselineNumber, ProjectId, and TaskId keys to get the specified task baseline. The query is all on one line.

https://<pwa_url>/_api/ProjectData/TaskBaselines
    ?$filter=BaselineNumber eq 1
    and ProjectId eq guid'76fecbe8-ada6-e111-9f30-78e7d101788a'
    and TaskId eq guid'79fecbe8-ada6-e111-9f30-78e7d101788a'

Definition

<EntityType Name="TaskBaseline">
  <Key>
    <PropertyRef Name="ProjectId" />
    <PropertyRef Name="TaskId" />
    <PropertyRef Name="BaselineNumber" />
  </Key>
  <Property Name="ProjectId" Type="Edm.Guid" Nullable="false" />
  . . .
  <NavigationProperty Name="Project" Relationship="ReportingData.TaskBaseline_Project" ToRole="Project" FromRole="TaskBaseline" />
  . . .
</EntityType>

Parent element

Element	Description
ReportingData	The schema for the reporting data in the ProjectData service.

Child elements

Child elements are properties of a task baseline and navigation properties of that task baseline. Attributes of the Property elements specify the property name and type, and whether the property can be a null value. The NavigationProperty elements specify collections of entities, such as tasks and projects, that are associated with a project. A navigation property uses an Association element in a query for a related entity collection

The Key elements specify the properties that are the primary keys for a task baseline query. ProjectId is the project GUID, TaskId is the task GUID, and BaselineNumber is the number of the task baseline.

Property elements

The following table lists the Property elements for the TaskBaseline entity. The Name, Type, and Nullable columns contain attribute values for each property.

Attribute values for the Property elements of TaskBaseline

Name	Type	Nullable	Description
BaselineNumber	Edm.Int32	false	Key A number that identifies a project baseline.
ProjectId	Edm.Guid	false	Key The GUID that identifies the project.
ProjectName	Edm.String	true	The name of the project.
TaskBaselineBudgetCost	Edm.Decimal	false	The cost of the budgeted amount of work as projected in the baseline.
TaskBaselineBudgetWork	Edm.Decimal	false	The budgeted amount of work as projected in the baseline.
TaskBaselineCost	Edm.Decimal	false	The total planned cost for a task. The baseline cost is known as budget at completion (BAC) for earned value.
TaskBaselineDeliverableFinishDate	Edm.DateTime	true	The published deliverable finish date and time for a task as projected in the baseline.
TaskBaselineDeliverableStartDate	Edm.DateTime	true	The published deliverable start date and time for a task.
Task BaselineDuration	Edm.Decimal	false	The amount of time estimated to complete a task.
TaskBaselineDurationString	Edm.String	true	A string that contains the projected task duration.
TaskBaselineFinishDate	Edm.DateTime	true	The projected completion date of a task.
TaskBaselineFinishDateString	Edm.String	true	A string that contains the projected task finish date and time.
TaskBaselineFixedCost	Edm.Decimal	false	A set task cost that is projected in the baseline and that remains constant regardless of the task duration or the work performed by a resource.
TaskBaselineStartDate	Edm.DateTime	true	The projected task start date and time.
TaskBaselineStartDateString	Edm.String	true	A string that contains the projected task start date and time.
TaskBaselineWork	Edm.Decimal	false	The total hours that are scheduled in the baseline projection for a task.
TaskId	Edm.Guid	false	Key The GUID that identifies the task.
TaskName	Edm.String	true	The name of the task.

NavigationProperty elements

The following table lists attribute values for the NavigationProperty elements of the TaskBaseline entity. The Name and Relationship columns contain attribute values for each navigation property.

There are two types of Relationship attributes. One type contains two pairs of names; each pair of names indicates a navigation direction. The first pair starts with the entity type that has the primary, or starting, role in the navigation. The second pair starts with the entity type that has the secondary, or dependent, role in the navigation. For example, for the Task navigation property, the primary type is TaskBaseline, and the secondary type is Task. For this type of navigation, the FromRole is TaskBaseline_Task, and the ToRole is Task_Baselines.

The other type of Relationship attribute contains a single pair of names. The first name in the pair is the primary entity type in the navigation. The second name in the pair is the secondary entity type in the navigation. For example, in the Project navigation property relationship, TaskBaseline is the primary entity type and Project is the secondary entity type.

Attribute values for the NavigationProperty elements

Name	Relationship	Description
Project	TaskBaseline_Project	Establishes navigation from a collection of task baselines to a project.
Task	TaskBaseline_Task_Task_Baselines	Establishes navigation from a collection of task baselines to a task and from a task to a baseline.
TaskBaselineTimephasedDataSet	TaskBaseline_TaskBaselineTimephasedDataSet_TaskBaselineTimephasedData_TaskBaselines	Establishes navigation from a collection of task baselines to a collection of task baseline timephased data and from a collection of task baseline timephased data to a collection of task baselines.

See also

Reference

TaskBaselines

ReportingData

Concepts

Querying OData feeds for Project 2013 reporting data