Page 7209 "CDS Couple Salespersons"
Base Application · Microsoft.Integration.D365Sales
Across versions
- BC23-25present
- BC26declaration changed
- BC27-30unchanged
Neighbourhood 4 connected objects and pages
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
- source table Table 5340 “CRM Systemuser”
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 5330 “CRM Integration Management” (3 calls:
OnInit → (object),ScheduleSalespersonsCoupling → CoupleCRMEntity,ScheduleUncoupledUsersSynch → CreateNewRecordsFromSelectedCRMRecords) - Codeunit 7201 “CDS Integration Impl.” (3 calls:
AddUsersToDefaultOwningTeam → AddUsersToDefaultOwningTeam,AddUsersToDefaultOwningTeam → GetDefaultOwningTeamMembership,OnInit → GetDefaultOwningTeamMembership) - Codeunit 5331 “CRM Coupling Management” (1 call:
ScheduleSalespersonsCoupling → RemoveCoupling)
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.