BC Observatoryunofficial, made by waldo
tableextensionPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table extension 705 "Error Message Extension"

Base Application · System.Utilities

Open in Claude705.mdSource on GitHub

Across versions

  1. BC23-25not present
  2. BC26added
  3. BC27-30unchanged

Neighbourhood 2 connected objects and pages

Table 700 "Error Message" (relates to)Error MessageCodeunit 700 "Page Management" (calls)Page Management

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 · System.Utilities · BC26-30 · source at ea08af5e · facts from BC29

Extends Error Message.

Events published

  • OnDrillDownSource(ErrorMessage: Record "Error Message"; SourceFieldNo: Integer; var IsHandled: Boolean) (integration)

Procedures

  • HandleDrillDown(SourceFieldNo: Integer)

Plus 2 local procedures.

Relations

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: "tableextension", object_name: "Error Message Extension"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources