Page 561 "CrossIntercomp. Partner Setup"

Base Application · Microsoft.Intercompany.DataExchange · captioned “IC Partner Cross-Environment Setup” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	IC Partner Cross-Environment Setup
SourceTable	IC Partner
PageType	NavigatePage
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
Review the terms and conditions	I accept	`ConsentState`	Accept the terms and conditions.
	LearnMore	`LearnMoreTok`	View information about the privacy.
Your connection details	Current Connection URL	`CurrentCompanyConnectionUrl`	—
	Current Company ID	`CurrentCompanyCompanyId`	—
	Intercompany ID	`CurrentCompanyIntercompanyId`	—
	Company Name	`CurrentCompanyName`	—
Intercompany Partner’s connection details	IC Partner’s Connection URL	`PartnerSaaSConnectionUrl`	Specifies the connection URL for the intercompany partner’s environment.
	IC Partner’s Company ID	`PartnerSaaSCompanyId`	Specifies the intercompany partner’s company ID in their environment.
	IC Partner’s Intercompany ID	Code	Specifies the intercompany partner’s intercompany identifier in their environment.
	IC Partner’s Company Name	`PartnerSaaSCompanyName`	Specifies the intercompany partner’s company name in their environment.
Authentication details	Client ID	`OAuth2ClientID`	Specifies the client ID of the Microsoft Entra authentication application.
	Client Secret	`OAuth2ClientSecret`	Specifies the client secret of the Microsoft Entra authentication application.
	Token Endpoint	`OAuth2TokenEndpoint`	Specifies the OAuth 2.0 token endpoint of the Microsoft Entra authentication application. The endpoint indicates a directory to which tokens can be requested. In most scenarios this will be: https://login.microsoftonline.com//oauth2/v2.0/token .
	Redirect URL	`OAuth2RedirectUrl`	Specifies the OAuth 2.0 redirect URL of the Microsoft Entra authentication application. In most scenarios this will be: https://businesscentral.dynamics.com/OAuthLanding.htm .

Actions

Group	Action	ToolTip
Processing	Test Connection	Test the connection to the partner’s company to check whether authentication is correctly set up.
	Back	Go to previous page
	Next	Go to the next page
	Finish	Finish the setup

Procedures

CheckIfSaaSConnectionDetailsAreFilled(): Boolean Δ BC25: Validates whether all required SaaS connection details are properly configured for API connectivity. Checks partner connection URL, company ID, OAuth credentials, and token endpoint configuration.
ValidateDynamicsUrl(Url: Text): Boolean + BC27 (internal)

Plus 9 local procedures.

Triggers

OnOpenPage, OnQueryClosePage

Relations

source table Table 413 “IC Partner”

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 489 “IC Partner Change Monitor” (2 calls: OnOpenPage → CheckHasPermissionsToChangeSensitiveFields, SaveConfigurationToTemporaryPartner → CheckHasPermissionsToChangeSensitiveFields)
Codeunit 560 “CrossIntercompany Connector” (2 calls: LoadSaaSDataForCurrentCompany → RemoveCurlyBracketsAndUpperCases, ValidateDynamicsUrl → IsDestinationUrlTrusted)

Recent changes

2026-09-14 #11378 [29.x][InterCompany][SII] Setup and telemetry enhancements (releases/29.x, BC29, feature)
2026-09-10 #11016 [AI Business Solutions] Enforce allow-listed Redirect URIs, token audiences and authorities for OAuth2 integrations (main, BC30, fix)

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: "CrossIntercomp. Partner Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.