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

Page 5360 "CRM Statistics FactBox"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 18 "Customer" (relates to)CustomerCodeunit 5330 "CRM Integration Management" (calls, 3 links)CRM Integration Management

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 “Dynamics 365 Sales Statistics” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dynamics 365 Sales Statistics
SourceTable Customer
PageType CardPart

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
Content Opportunities GetNoOfCRMOpportunities() Specifies the sales opportunity that is coupled to this Dynamics 365 Sales opportunity.
Quotes GetNoOfCRMQuotes() Specifies information related to the Dynamics 365 Sales connection.
Cases GetNoOfCRMCases() Specifies information related to the Dynamics 365 Sales connection.

Procedures

3 local procedures, no public ones.

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 Statistics FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources