Page 14 "Salespersons/Purchasers"
Base Application · Microsoft.CRM.Team
Across versions
- BC23-25present
- BC26declaration changed
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 8 connected objects and pages
Base Application · Microsoft.CRM.Team · captioned “Salespeople/Purchasers” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Salespeople/Purchasers |
| SourceTable | Salesperson/Purchaser |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Basic, 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 |
|---|---|---|---|
| Control1 | Code | Code | Specifies the code of the record. |
| Name | Name | Specifies the name of the record. | |
| Commission % | Commission % | Specifies the percentage to use to calculate the salesperson’s commission. from the table field | |
| Phone No. | Phone No. | Specifies the salesperson’s or purchaser’s telephone number. | |
| Privacy Blocked | Privacy Blocked | Specifies whether to limit access to data for the data subject during daily operations. This is useful, for example, when protecting data from changes while it is under privacy review. from the table field | |
| Coupled to Dataverse | Coupled to Dataverse | Specifies that the salesperson/purchaser is coupled to a user in Dataverse. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Salesperson | Teams | View or edit any teams that the salesperson/purchaser is a member of. | Page 5107 “Salesperson Teams” |
| Contacts | View a list of contacts that are associated with the salesperson/purchaser. | Page 5052 “Contact List” | |
| Dimensions | Dimensions-Single | View or edit the single set of dimensions that are set up for the selected record. | Page 540 “Default Dimensions” |
| Dimensions-Multiple | View or edit dimensions for a group of records. You can assign dimension codes to transactions to distribute costs and analyze historical information. | ||
| Salesperson | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 5117 “Salesperson Statistics” |
| Campaigns | View or edit any campaigns that the salesperson/purchaser is assigned to. | Page 5087 “Campaign List” | |
| Segments | View a list of all segments. | Page 5093 “Segment List” | |
| Interaction Log Entries | View a list of the interactions that you have logged, for example, when you create an interaction, print a cover sheet, a sales order, and so on. | Page 5076 “Interaction Log Entries” | |
| Postponed Interactions | View postponed interactions for the salesperson/purchaser. | Page 5082 “Postponed Interactions” | |
| Tasks | View tasks for the salesperson/purchaser. | Page 5096 “Task List” | |
| Opportunities | View opportunities for the salesperson/purchaser. | Page 5123 “Opportunity List” | |
| Dataverse | User | Open the coupled Dataverse system user. | |
| Synchronize | Send or get updated data to or from Dataverse. | ||
| Coupling | Set Up Coupling | Create or modify the coupling to a Dataverse user. | |
| Match-Based Coupling | Couple salespeople to users in Dataverse based on criteria. | ||
| Delete Coupling | Delete the coupling to a Dataverse user. | ||
| Dataverse | Synchronization Log | View integration synchronization jobs for the salesperson/purchaser table. | |
| History | Sent Emails | View a list of emails that you have sent to this salesperson/purchaser. | |
| Processing | Create Interaction | Use a batch job to help you create interactions for the involved salespeople or purchasers. | |
| Send Email | Send an email to this person. |
Procedures
GetSelectionFilter(): Text
Triggers
OnAfterGetCurrRecord, OnInit, OnOpenPage
Relations
- card page Page 5116 “Salesperson/Purchaser Card”
- source table Table 13 “Salesperson/Purchaser”
Pages and codeunits on this table
- Table 13 “Salesperson/Purchaser” (lookup page)
Extended by
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” (2 calls:
OnOpenPage → IsCDSIntegrationEnabled,OnOpenPage → IsCRMIntegrationEnabled) - Codeunit 46 “SelectionFilterManagement” (1 call:
GetSelectionFilter → GetSelectionFilterForSalesPersonPurchaser) - Codeunit 5331 “CRM Coupling Management” (1 call:
OnAfterGetCurrRecord → IsRecordCoupledToCRM)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "Salespersons/Purchasers"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.