codeunitRelationship Managementofficial - Microsoftderived - from the source, no model text

Codeunit 1638 "Office Jobs Handler"

Base Application · Microsoft.CRM.Outlook

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Table 1600 "Office Add-in Context" (relates to)Office Add-in ContextPage 1615 "Office Job Journal" (calls, 3 links)Office Job JournalCodeunit 1004 "Job Transfer Line" (calls)Job Transfer LineCodeunit 1630 "Office Management" (calls)Office ManagementCodeunit 1632 "Office Error Engine" (calls)Office Error Engine

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

Properties

Property Value
TableNo Office Add-in Context

Procedures

  • IsJobsHostType(OfficeAddinContext: Record "Office Add-in Context"): Boolean
  • GetJobProperties(OfficeAddinContext: Record "Office Add-in Context"; var JobNo: Text; var JobTaskNo: Text; var JobPlanningLineNo: Integer)
  • SubmitJobPlanningLine(JobPlanningLine: Record "Job Planning Line"; JobJournalTemplateName: Code[10]; JobJournalBatchName: Code[10])
  • SetJobJournalRange(var JobJournalLine: Record "Job Journal Line"; JobPlanningLine: Record "Job Planning Line")

Plus 1 local procedures.

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.

Called by

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

Evidence 1 sources