Page 224 "Res. Capacity Entries"

Base Application · Microsoft.Projects.Resources.Resource · captioned “Resource Capacity Entries” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Resource Capacity Entries
SourceTable	Res. Capacity Entry
PageType	List
UsageCategory	History
ApplicationArea	Jobs

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
Control1	Date	Date	Specifies the date for which the capacity entry is valid. from the table field
	Resource No.	Resource No.	Specifies the number of the corresponding resource. from the table field
	Resource Group No.	Resource Group No.	Specifies the number of the corresponding resource group assigned to the resource. from the table field
	Capacity	Capacity	Specifies the capacity that is calculated and recorded. The capacity is in the unit of measure. from the table field
	Entry No.	Entry No.	Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field

Relations

source table Table 160 “Res. Capacity Entry”

Pages and codeunits on this table

Table 160 “Res. Capacity Entry” (drill-down page)
Table 160 “Res. Capacity Entry” (lookup page)

Called by

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 952 “Time Sheet Chart Mgt.” (1 call: DrillDown → (object))

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Res. Capacity Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.