tableProjectsofficial - Microsoftderived - from the source, no model text

Table 240 "Resource Register"

Base Application · Microsoft.Projects.Resources.Ledger

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC262 procedures added, 1 procedures changed
  5. BC27unchanged
  6. BC288 fields changed
  7. BC29-30unchanged

Neighbourhood 7 connected objects and pages

Table 203 "Res. Ledger Entry" (relates to, 2 links)Res. Ledger EntryTable 230 "Source Code" (relates to)Source CodePage 274 "Resource Registers" (pages and codeunits on it, 3 links)Resource RegistersCodeunit 275 "Res. Reg.-Show Ledger" (pages and codeunits on it)Res. Reg.-Show LedgerCodeunit 703 "Find Record Management" (calls)Find Record ManagementTable 203 "Res. Ledger Entry" (referenced by)Res. Ledger EntryTable 87 "Date Compr. Register" (referenced by)Date Compr. Register

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Projects.Resources.Ledger · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Resource 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 203 “Res. Ledger Entry” (Res. Ledger Entry)
3 To Entry No. Δ BC28 Integer Specifies the number of the last entry line that you included before you posted the entries in the journal. TableRelation Table 203 “Res. Ledger Entry” (Res. Ledger Entry)
4 Creation Date Δ BC28 Date Specifies the date when 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 when 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 + BC26
  • GetNextEntryNo(): Integer + BC26 + BC26
  • GetLastEntryNo(): Integer Δ BC26

Relations

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

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.

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: "Resource Register"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources