Codeunit 1291 "DotNet Exception Handler"
Base Application · System.Utilities
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · System.Utilities · BC23-30 · source at ea08af5e · facts from BC29
Procedures
Catch(var Exception: DotNet Exception; Type: DotNet Type)Collect()TryCastToType(Type: DotNet Type): BooleanCastToType(var Exception: DotNet Exception; Type: DotNet Type): BooleanGetMessage(): TextRethrow()
Plus 1 local procedures.
Triggers
OnRun
Called by
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 7201 “CDS Integration Impl.” (7 calls:
EnrichWithDotNetException → Collect,EnrichWithDotNetException → GetMessage,ProcessConnectionFailures → CastToType, …) - Codeunit 5330 “CRM Integration Management” (5 calls:
ProcessConnectionFailures → CastToType,ProcessConnectionFailures → Collect,ProcessConnectionFailures → GetMessage, …) - Codeunit 1299 “Web Request Helper” (3 calls:
GetWebResponseError → CastToType,GetWebResponseError → Collect,GetWebResponseError → Rethrow) - Codeunit 1545 “Workflow Webhook Notification” (2 calls:
Notify → CastToType,Notify → Collect)
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: "codeunit", object_name: "DotNet Exception Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.