Association: CostConstraintScenario_CreatedByResource (ProjectData service)
In this article
Definition
Attributes
Parent element
Child elements
The CostConstraintScenario_CreatedByResource association relates cost constraint scenarios to a resource.
Definition
<Association Name="CostConstraintScenario_CreatedByResource">
<End Type="ReportingData.Resource" Role="CreatedByResource" Multiplicity="0..1" />
<End Type="ReportingData.CostConstraintScenario" Role="CostConstraintScenario" Multiplicity="*" />
</Association>
Attributes
Attribute |
Value |
Description |
|---|---|---|
Name |
CostConstraintScenario_CreatedByResource |
Identifies the two entity types that form the CostConstraintScenario_CreatedByResource association. |
Parent element
Element |
Description |
|---|---|
The schema for the reporting data in the ProjectData service. |
Child elements
The CostConstraintScenario_CreatedByResource association element contains two End elements that represent opposite ends of the association. The Role attribute is a lookup key that enables a navigational property to specify the direction in the association. The Multiplicity attribute refers to the entity type. Multiplicity indicates the number of entities that can be related at each end of the association: zero or one (0..1), or many (*). The Microsoft .NET implementation of OData uses 0..1 when the navigational property points to a single entity, rather than to an entity set.
Attributes of the End elements for the CostConstraintScenario_CreatedByResource association
Role |
Type |
Multiplicity |
Description |
|---|---|---|---|
CostConstraintScenario |
* |
The collection of cost constraint scenarios in the reporting tables. |
|
CreatedByResource |
0..1 |
The resource object that is referenced in the CostConstraintScenario_CreatedByResource association. |
Remarks
The CreatedByResource navigation property of the CostConstraintScenario entity type uses the CostConstraintScenario_CreatedByResource association to query for a resource that is associated with a collection of cost constraint scenarios.