Page 278 "Job Registers"

Base Application · Microsoft.Projects.Project.Ledger · captioned “Project Registers” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Project Registers
SourceTable	Job Register
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	No.	No.	Specifies the number of the involved entry or record, according to the specified number series. from the table field
	Creation Date	Creation Date	Specifies the date on which you posted the entries in the journal. from the table field
	Creation Time	Creation Time	Specifies the time on which you posted the entries in the journal. from the table field
	User ID	User ID	Specifies the ID of the user who posted the entry, to be used, for example, in the change log. from the table field
	Source Code	Source Code	Specifies the source code that specifies where the entry was created. from the table field
	Journal Batch Name	Journal Batch Name	Specifies the name of the journal batch, a personalized journal layout, that the entries were posted from. from the table field
	From Entry No.	From Entry No.	Specifies the first item entry number in the register. from the table field
	To Entry No.	To Entry No.	Specifies the entry number of the last entry line you included before you posted the entries in the journal. from the table field

Actions

Group	Action	ToolTip	Runs
Register	Project Ledger	View the project ledger entries.	Codeunit 1025 “Job Reg.-Show Ledger”

Relations

source table Table 241 “Job Register”

Pages and codeunits on this table

Table 241 “Job Register” (drill-down page)
Table 241 “Job Register” (lookup page)

Ask your agent

Procedure bodies are not stored here (D10). 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: "Job Registers"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 2 connected objects and pages