pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 5362 "CRM UnitGroup List"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 5362 "CRM Uomschedule" (relates to)CRM UomscheduleCodeunit 5330 "CRM Integration Management" (calls, 2 links)CRM Integration ManagementCodeunit 5332 "Lookup CRM Tables" (calls)Lookup CRM Tables

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.Integration.D365Sales · captioned “Unit Groups - Microsoft Dynamics 365 Sales” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Unit Groups - Microsoft Dynamics 365 Sales
SourceTable CRM Uomschedule
PageType List
UsageCategory Lists
ApplicationArea Suite

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
Control2 Name Name Specifies the name of the record. from the table field
Base Unit Name BaseUoMName Specifies the base unit of measure of the Dynamics 365 Sales record. from the table field
Status StateCode Specifies information related to the Dynamics 365 Sales connection.
Status Reason StatusCode Specifies information related to the Dynamics 365 Sales connection.
Coupled Coupled Specifies if the Dynamics 365 Sales record is coupled to Business Central.

Actions

Group Action ToolTip Runs
Processing Hide Coupled Unit Groups Do not show coupled unit groups.
Show Coupled Unit Groups Show coupled unit groups.

Procedures

  • SetCurrentlyCoupledCRMUomschedule(CRMUomschedule: Record "CRM Uomschedule")

Triggers

OnAfterGetRecord, OnInit, OnOpenPage

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.

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: "CRM UnitGroup List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources