BC Observatoryunofficial, made by waldo
codeunitHuman Resourcesofficial - Microsoftderived - from the source, no model text

Codeunit 5201 "Employee/Salesperson Update"

Base Application · Microsoft.HumanResources.Employee

Open in Claude5201.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Table 5200 "Employee" (calls)Employee

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.HumanResources.Employee · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Permissions TableData “Salesperson/Purchaser” = rimd

Events published

  • OnAfterShouldRunUpdate(OldEmployee: Record Employee; Employee: Record Employee; var Result: Boolean) (integration)
  • OnSalesPersonUpdateOnBeforeModify(Employee: Record Employee; var SalespersonPurchaser: Record "Salesperson/Purchaser") (integration)
  • OnBeforeShouldRunUpdate(OldEmployee: Record Employee; Employee: Record Employee; var Result: Boolean; var IsHandled: Boolean) (integration)

Procedures

  • HumanResToSalesPerson(OldEmployee: Record Employee; Employee: Record Employee)

Plus 2 local procedures.

Triggers

OnRun

Called by

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: "codeunit", object_name: "Employee/Salesperson Update"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources