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

Report 5911 "Service - Invoice"

Base Application · Microsoft.Service.History

Across versions

  1. BC23-30present

Neighbourhood 8 connected objects and pages

Report extension 6170 "PostedServiceInvoiceWithQR" (extended by)PostedServiceInvoiceWithQRCodeunit 368 "Format Document" (calls, 5 links)Format DocumentCodeunit 6001 "Service Format Address" (calls, 2 links)Service Format AddressCodeunit 365 "Format Address" (calls)Format AddressCodeunit 43 "Language" (calls)LanguageCodeunit 9520 "Mail Management" (calls)Mail ManagementService - Invoice (document report) (Learn pages)Service - Invoice (document …Service management reports (Learn pages)Service management reports

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

Properties

Property Value
Caption Service - Invoice
DefaultLayout RDLC
Permissions TableData “Sales Shipment Buffer” = rimd

Events published

  • OnBeforeGetDocumentCaption(ServiceInvoiceHeader: Record "Service Invoice Header"; var DocCaption: Text) (integration)

Procedures

  • FindPostedShipmentDate(): Date
  • GenerateBufferFromValueEntry(ServiceInvoiceLine2: Record "Service Invoice Line")
  • GenerateBufferFromShipment(ServiceInvoiceLine: Record "Service Invoice Line")
  • AddBufferEntry(ServiceInvoiceLine: Record "Service Invoice Line"; QtyOnShipment: Decimal; PostingDate: Date)
  • FindDimTxt(DimSetID: Integer)

Plus 7 local procedures.

Triggers

OnInitReport

Extended by

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.

Recent changes

Countries that replace it

IT

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 3 sources