Page 5116 "Salesperson/Purchaser Card"

Base Application · Microsoft.CRM.Team · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Salesperson/Purchaser Card
SourceTable	Salesperson/Purchaser
PageType	Card

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
General	Code	Code	Specifies a code for the salesperson or purchaser. from the table field
	Name	Name	Specifies the name of the salesperson or purchaser. from the table field
	Job Title	Job Title	Specifies the salesperson’s job title. from the table field
	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 telephone number. from the table field
	E-Mail	E-Mail	Specifies the salesperson’s email address. from the table field
	Next Task Date	Next Task Date	Specifies the date of the next task assigned to the salesperson. from the table field
	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
	Blocked	Blocked	Specifies whether this Salesperson can be assigned for new documents from the table field
Invoicing	Global Dimension 1 Code	Global Dimension 1 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
	Global Dimension 2 Code	Global Dimension 2 Code	Specifies the code for the global dimension that is linked to the record or entry for analysis purposes. Two global dimensions, typically for the company’s most important activities, are available on all cards, documents, reports, and lists. from the table field
FactBoxes	Control3	part Page 5108 “Salesperson/Purchaser Picture”	—

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	View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.	Page 540 “Default Dimensions”
	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 interaction log entries for the salesperson/purchaser.	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.
	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	Create an interaction with a specified contact.
	Send Email	Send an email to this person.

Triggers

OnAfterGetCurrRecord, OnInsertRecord, OnOpenPage

Relations

source table Table 13 “Salesperson/Purchaser”

Pages and codeunits on this table

Page 14 “Salespersons/Purchasers” (card page)

Extended by

Page extension 20647 “Salesperson/Purchaser Card BF”

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: OnAfterGetCurrRecord → SendResultNotification, OnOpenPage → IsCDSIntegrationEnabled, OnOpenPage → IsCRMIntegrationEnabled)
Codeunit 5331 “CRM Coupling Management” (1 call: OnAfterGetCurrRecord → IsRecordCoupledToCRM)

Called by

Codeunit 5330 “CRM Integration Management” (1 call: OpenRecordCardPage → (object))
Page 5197 “Attendee Subform” (1 call: ShowCard → (object))

Documented on Microsoft Learn

Set up purchasers and assign purchasers to vendors

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: "Salesperson/Purchaser Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.