Page 566 "IC Connection Details"

Base Application · Microsoft.Intercompany.DataExchange · captioned “Connection Details” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Connection Details
PageType	StandardDialog
UsageCategory	Administration
ApplicationArea	Intercompany

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
Your connection details	Connection URL	`CompanyConnectionUrl`	Specifies the URL to share with intercompany partners that want to share data with the current company across environments.
	Company ID	`CompanyCompanyId`	Specifies the unique GUID that identifies the current company.
	Intercompany ID	`CompanyIntercompanyId`	Specifies the intercompany ID that intercompany partners should use when they share data with the current company.
	Company Name	`CompanyName`	Specifies the company name of the current company.

Triggers

OnOpenPage

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 560 “CrossIntercompany Connector” (1 call: OnOpenPage → RemoveCurlyBracketsAndUpperCases)

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: "page", object_name: "IC Connection Details"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.