codeunitProjectsofficial - Microsoftderived - from the source, no model text

Codeunit 1016 "Jobs-Send"

Base Application · Microsoft.Projects.Project.Job

Across versions

  1. BC23-27present
  2. BC281 procedures added, 1 events added
  3. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Table 167 "Job" (relates to)JobCodeunit 1630 "Office Management" (calls, 2 links)Office ManagementCodeunit 5139 "Job Archive Management" (calls)Job Archive ManagementPage 365 "Post and Send Confirmation" (calls)Post and Send Confirmation

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.Projects.Project.Job · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
TableNo Job

Events published

  • OnBeforeCode(var Job: Record Job; var IsHandled: Boolean) + BC28 (integration)

Procedures

4 local procedures, no public ones.

Triggers

OnRun

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: "codeunit", object_name: "Jobs-Send"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources