Table 241 "Job Register"
Base Application · Microsoft.Projects.Project.Ledger
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC263 procedures added
- BC27unchanged
- BC288 fields changed
- BC29-30unchanged
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Projects.Project.Ledger · captioned “Project Register” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Project Register |
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | No. Δ BC28 | Integer | Specifies the number of the involved entry or record, according to the specified number series. | |
| 2 | From Entry No. Δ BC28 | Integer | Specifies the first item entry number in the register. | TableRelation Table 169 “Job Ledger Entry” (Job Ledger Entry) |
| 3 | To Entry No. Δ BC28 | Integer | Specifies the entry number of the last entry line you included before you posted the entries in the journal. | TableRelation Table 169 “Job Ledger Entry” (Job Ledger Entry) |
| 4 | Creation Date Δ BC28 | Date | Specifies the date on which you posted the entries in the journal. | |
| 5 | Source Code Δ BC28 | Code[10] | Specifies the source code that specifies where the entry was created. | TableRelation Table 230 “Source Code” (Source Code) |
| 6 | User ID Δ BC28 | Code[50] | Specifies the ID of the user who posted the entry, to be used, for example, in the change log. | TableRelation User.“User Name”; DataClassification EndUserIdentifiableInformation |
| 7 | Journal Batch Name Δ BC28 | Code[10] | Specifies the name of the journal batch, a personalized journal layout, that the entries were posted from. | |
| 9 | Creation Time Δ BC28 | Time | Specifies the time on which you posted the entries in the journal. |
Keys
- Key1: No. (clustered)
- Key2: Creation Date
- Key3: Source Code, Journal Batch Name, Creation Date
Procedures
GetNextEntryNo(UseLegacyPosting: Boolean): Integer+ BC26 + BC26GetNextEntryNo(): Integer+ BC26 + BC26GetLastEntryNo(): Integer+ BC26
Relations
- drill-down page Page 278 “Job Registers”
- lookup page Page 278 “Job Registers”
- From Entry No.: TableRelation Table 169 “Job Ledger Entry”
- To Entry No.: TableRelation Table 169 “Job Ledger Entry”
- Source Code: TableRelation Table 230 “Source Code”
Referenced by
1 fields in 1 objects relate to this table (TableRelation or CalcFormula).
- Table 169 “Job Ledger Entry”: Job Register No.
Pages and codeunits on this table
- Page 278 “Job Registers” (source table)
- Codeunit 1025 “Job Reg.-Show Ledger” (codeunit runs on it)
Calls
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 703 “Find Record Management” (1 call:
GetLastEntryNo → GetLastEntryIntFieldValue)
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: "table", object_name: "Job Register"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.