BC Observatoryunofficial, made by waldo
reportService Managementofficial - Microsoftderived - from the source, no model text

Report 6007 "Insert Fault/Resol. Relations"

Base Application · Microsoft.Service.Maintenance

Open in Claude6007.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 5913 "FaultResolRelation-Calculate" (calls)FaultResolRelation-Calculate

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.Maintenance · captioned “Insert Fault/Resolution Codes Relationships” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Insert Fault/Resolution Codes Relationships
UsageCategory Tasks
ApplicationArea Service

Procedures

  • InitializeRequest(DateFrom: Date; ToDateFrom: Date; BasedOnServItemGrFrom: Boolean; RetainManuallyInsertedFrom: Boolean)

Triggers

OnInitReport, OnPostReport, 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.

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: "Insert Fault/Resol. Relations"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources