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

Report 5914 "Delete Invoiced Service Orders"

Base Application · Microsoft.Service.Document

Across versions

  1. BC23present
  2. BC241 events added, 1 events removed
  3. BC25unchanged
  4. BC26declaration changed
  5. BC27-28unchanged
  6. BC29declaration changed
  7. BC30unchanged

Neighbourhood 1 connected objects and pages

Codeunit 8714 "Audit Log" (calls)Audit Log

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

Properties

Property Value
Caption Delete Invoiced Service Orders
UsageCategory Tasks
ApplicationArea Service

Events published

  • OnBeforeDeleteServiceHeader(var ServiceHeader: Record "Service Header") (integration)
  • OnBeforeDeleteServiceOrderLine(ServiceLine: Record "Service Line") (integration)
  • OnBeforeDeleteServiceOrderItemLine(ServiceItemLine: Record "Service Item Line") (integration)
  • OnBeforeServiceHeaderOnAfterGetRecord(var ServiceHeader: Record "Service Header"; var IsHandled: Boolean; var ProgressDialog: Dialog) + BC24 − BC24 (integration)

Triggers

OnPostReport

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: "report", object_name: "Delete Invoiced Service Orders"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources