Page 1836 "Consolidation Log Entry"
Base Application · Microsoft.Finance.Consolidation
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Finance.Consolidation · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Consolidation Log Entry |
| SourceTable | Consolidation Log Entry |
| PageType | Card |
| UsageCategory | None |
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 |
|---|---|---|---|
| Content | Entry No. | Entry No. | The unique identifier of the log entry. from the table field |
| Created at | Rec.SystemCreatedAt |
The date and time when the log entry was created. | |
| Status Code | Status Code | The status code of the response that was received from the API for this request. from the table field | |
| Request | Rec.GetRequestAsText() |
The request that was sent to the API of the business unit. | |
| Response | Rec.GetResponseAsText() |
The response that was received from the API for this request. |
Relations
- source table Table 1834 “Consolidation Log Entry”
Pages and codeunits on this table
- Page 1835 “Consolidation Log Entries” (card 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: "Consolidation Log Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.