Table 1834 "Consolidation Log Entry"

Base Application · Microsoft.Finance.Consolidation · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Consolidation Log Entry
Access	Internal
DataClassification	SystemMetadata

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	Entry No. Δ BC29	BigInteger	The unique identifier of the log entry.	AutoIncrement
2	Request URI	Blob	—
3	Response	Blob	—
4	Status Code Δ BC29	Integer	The status code of the response that was received from the API for this request.
5	Request URI Preview Δ BC29	Text[50]	The URI of the request that was sent to the API of the business unit.

Keys

Key1: Entry No. (clustered)

Procedures

GetRequestAsText(): Text (internal)
GetResponseAsText(): Text (internal)

Pages and codeunits on this table

Page 1835 “Consolidation Log Entries” (source table)
Page 1836 “Consolidation Log Entry” (source 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.

Codeunit 10 “Type Helper” (4 calls: GetRequestAsText → LFSeparator, GetRequestAsText → ReadAsTextWithSeparator, GetResponseAsText → LFSeparator, …)

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