Codeunit 1034 "Job Planning Line - Calendar"

Base Application · Microsoft.Projects.Project.Planning · BC23-30 · source at ea08af5e · facts from BC29

Properties

Events published

• OnAfterSetPlanningLine(NewJobPlanningLine: Record "Job Planning Line"; var ProjectManagerResource: Record Resource) (integration)
• OnAfterGetStartDate(JobPlanningLine: Record "Job Planning Line"; var StartDateTime: Text) (integration)
• OnAfterGetEndDate(JobPlanningLine: Record "Job Planning Line"; var EndDateTime: Text) (integration)

Event subscriptions

• OnDeletePlanningLine subscribes to Table “Job Planning Line” OnAfterDeleteEvent

Procedures

• SetPlanningLine(NewJobPlanningLine: Record "Job Planning Line")
• CreateAndSend()
• CreateRequest(var TempEmailItem: Record "Email Item" temporary): Boolean
• CreateCancellation(var TempEmailItem: Record "Email Item" temporary): Boolean

Plus 13 local procedures.

Triggers

OnRun

Relations

• runs on Table 1003 “Job Planning Line”

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 4100 “Temp Blob” (2 calls: GenerateEmail → CreateInStream, GenerateEmail → CreateOutStream)
• Codeunit 1630 “Office Management” (1 call: CreateAndSend → GetOfficeAddinTelemetryCategory)
• Codeunit 3960 “Regex” (1 call: GetHtmlDescription → Replace)
• Codeunit 8893 “Email Scenario” (1 call: GetOrganizer → GetEmailAccount)

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: "Job Planning Line - Calendar"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.