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

Report 5915 "Service Document - Test"

Base Application · Microsoft.Service.Reports

Across versions

  1. BC23-25present
  2. BC261 events added
  3. BC27-30unchanged

Neighbourhood 5 connected objects and pages

Codeunit 4812 "Intrastat Report Doc. Compl." (event subscribers)Intrastat Report Doc. Compl.Codeunit 408 "DimensionManagement" (calls, 3 links)DimensionManagementCodeunit 5700 "User Setup Management" (calls)User Setup ManagementService Document - Test (report) (Learn pages)Service Document - Test (rep…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.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Service Document - Test
DefaultLayout RDLC

Events published

  • OnAfterCheckServiceDoc(ServiceHeader: Record "Service Header"; var ErrorText: array[99] of Text[250]; var ErrorCounter: Integer) + BC26 (integration)
  • OnBeforeCheckType(ServiceLine: Record "Service Line"; var ErrorCounter: Integer; var ErrorText: array[99] of Text[250]) (integration)

Procedures

  • FindDimTxt(DimSetID: Integer)
  • CheckQuantity(var ServiceLine: Record "Service Line")
  • InitializeRequest(ShipReceiveOnNextPostReqFrom: Boolean; InvOnNextPostReqFrom: Boolean; ShowDimFrom: Boolean)

Plus 6 local procedures.

Triggers

OnInitReport, OnPreReport

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.

Countries that replace it

CA, IT, MX, US

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

Evidence 3 sources