Page 679 "IC API Log Entry"

Base Application · Microsoft.Intercompany.DataExchange · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	IC API Log Entry
SourceTable	IC API Log
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
General	Entry No.	Entry No.	Specifies the unique identifier of the log entry.
	Created at	`Rec.SystemCreatedAt`	Specifies the date and time when the log entry was created.
	IC Partner Code	IC Partner Code	Specifies the intercompany partner code related to this API call.
	Direction	Direction	Specifies whether this was an outgoing or incoming API call.
	Method	Method	Specifies the HTTP method used for the API call.
	Status Code	Status Code	Specifies the HTTP status code returned by the API call.
Request	Request URI	`Rec.GetRequestURIAsText()`	Specifies the full URI of the API request.
	Request Body	`Rec.GetRequestBodyAsText()`	Specifies the JSON body sent in the API request.
Response	Response Body	`Rec.GetResponseBodyAsText()`	Specifies the JSON body received in the API response.

Relations

source table Table 444 “IC API Log”

Pages and codeunits on this table

Page 621 “IC API 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: "IC API Log Entry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.