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

Page 7209 "CDS Couple Salespersons"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23-25present
  2. BC26declaration changed
  3. BC27-30unchanged

Neighbourhood 4 connected objects and pages

Table 5340 "CRM Systemuser" (relates to)CRM SystemuserCodeunit 5330 "CRM Integration Management" (calls, 3 links)CRM Integration ManagementCodeunit 7201 "CDS Integration Impl." (calls, 3 links)CDS Integration Impl.Codeunit 5331 "CRM Coupling Management" (calls)CRM Coupling 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 “Couple Dataverse Users with Salespeople” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption ‘Couple Dataverse Users with Salespeople’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’
SourceTable CRM Systemuser
PageType List

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 User Name Dataverse FullName ‘Specifies data from a corresponding column in a Dataverse table.’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’
Email Address InternalEMailAddress Specifies the email address. from the table field
Salesperson (Business Central) TempCRMSystemuser.FirstName Specifies the code for the salesperson or purchaser.
Default Team Member TeamMember Specifies whether the user is associated with the default team in Dataverse.

Actions

Group Action ToolTip Runs
Create Salesperson Create Salesperson Create the Dataverse user as a salesperson in Business Central.
Delete Coupling Delete the coupling between the user in Dataverse and salesperson in Business Central.
Match-Based Coupling Couple salespeople to users in Dataverse based on criteria.

Procedures

  • SetCurrentlyCoupledCRMSystemuser(CRMSystemuser: Record "CRM Systemuser")
  • Initialize(var NewCrmHelper: DotNet CrmHelper)

Plus 7 local procedures.

Triggers

OnAfterGetRecord, OnInit, 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.

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: "CDS Couple Salespersons"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources