pageFinanceofficial - Microsoftderived - from the source, no model text

Page 565 "CrossIntercompany Modify Setup"

Base Application · Microsoft.Intercompany.DataExchange

Across versions

  1. BC23present
  2. BC242 procedures added
  3. BC25-30unchanged

Neighbourhood 3 connected objects and pages

Table 413 "IC Partner" (relates to)IC PartnerCodeunit 489 "IC Partner Change Monitor" (calls, 2 links)IC Partner Change MonitorCodeunit 560 "CrossIntercompany Connector" (calls, 2 links)CrossIntercompany Connector

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 · captioned “Intercompany External Setup” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Intercompany External Setup
SourceTable IC Partner
PageType StandardDialog
UsageCategory None
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
DataExchangeInformation IC Partner Code Code Specifies the intercompany partner code.
IC Partner’s Connection URL ConnectionUrl Specifies the connection URL for the intercompany partner’s environment.
IC Partner’s Company ID CompanyId Specifies the intercompany partner’s company ID in their environment.
Client ID ClientId Specifies the client ID of the Microsoft Entra authentication application.
Client Secret NewClientSecret Specifies the client secret of the Microsoft Entra authentication application.
Token Endpoint TokenEndpoint Specifies the OAuth 2.0 token endpoint of the Microsoft Entra authentication application.
Redirect URL RedirectUrl Specifies the OAuth 2.0 redirect URL of the Microsoft Entra authentication application.

Procedures

3 local procedures, no public ones.

Triggers

OnOpenPage, OnQueryClosePage

Relations

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.

Recent changes

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

Evidence 1 sources