Report 5915 "Service Document - Test"
Base Application · Microsoft.Service.Reports
Across versions
- BC23-25present
- BC261 events added
- BC27-30unchanged
Neighbourhood 5 connected objects and pages
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)- subscribers: Codeunit 4812 “Intrastat Report Doc. Compl.” CheckIntrastatMandatoryFieldsOnAfterCheckServiceDocServiceDocumentTest
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.
- Codeunit 408 “DimensionManagement” (3 calls:
CheckShptLines → CheckDimIDConsistency,CheckShptLines → GetDimensionSet,CheckShptLines → GetDocDimConsistencyErr) - Codeunit 5700 “User Setup Management” (1 call:
VerifyPostingDate → TestAllowedPostingDate)
Countries that replace 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 Document - Test"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.