tableFinanceofficial - Microsoftderived - from the source, no model text

Table 444 "IC API Log"

Base Application · Microsoft.Intercompany.DataExchange

Across versions

  1. BC23-28not present
  2. BC29added
  3. BC30unchanged

Neighbourhood 4 connected objects and pages

Page 621 "IC API Log Entries" (pages and codeunits on it)IC API Log EntriesPage 679 "IC API Log Entry" (pages and codeunits on it)IC API Log EntryCodeunit 10 "Type Helper" (calls, 6 links)Type HelperSet up intercompany transaction posting (Learn pages)Set up intercompany transact…

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.Intercompany.DataExchange · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 621 “IC API Log Entries” (1 Learn page).

Properties

Property Value
Caption IC API Log
Access Internal
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 Entry No. BigInteger Specifies the unique identifier of the log entry. via Page 679 “IC API Log Entry” AutoIncrement; DataClassification SystemMetadata
2 IC Partner Code Code[20] Specifies the intercompany partner code related to this API call. via Page 679 “IC API Log Entry”
3 Direction Option Specifies whether this was an outgoing or incoming API call. via Page 679 “IC API Log Entry” OptionCaption: Outgoing,Incoming; DataClassification SystemMetadata
4 Method Text[10] Specifies the HTTP method used for the API call. via Page 679 “IC API Log Entry” DataClassification SystemMetadata
5 Request URI Blob —
6 Request URI Preview Text[250] Specifies the URI of the API request. via Page 621 “IC API Log Entries”
7 Request Body Blob — DataClassification EndUserIdentifiableInformation
8 Response Body Blob — DataClassification EndUserIdentifiableInformation
9 Status Code Integer Specifies the HTTP status code returned by the API call. via Page 679 “IC API Log Entry” DataClassification SystemMetadata

Keys

  • Key1: Entry No. (clustered)

Procedures

  • GetRequestURIAsText(): Text (internal)
  • GetRequestBodyAsText(): Text (internal)
  • GetResponseBodyAsText(): Text (internal)
  • LogEntry(PartnerCode: Code[20]; DirectionValue: Option; MethodValue: Text; Uri: Text; RequestContent: Text; ResponseContent: Text; StatusCodeValue: Integer) (internal)

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.

  • Codeunit 10 “Type Helper” (6 calls: GetRequestBodyAsText → LFSeparator, GetRequestBodyAsText → ReadAsTextWithSeparator, GetRequestURIAsText → 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: "IC API Log"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources