Codeunit 9654 "Design-time Report Selection"
Base Application · Microsoft.Foundation.Reporting
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Foundation.Reporting · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SingleInstance | true |
Procedures
SetSelectedCustomLayout(NewCustomLayoutCode: Code[20])GetSelectedCustomLayout(): Code[20]SetSelectedLayout(LayoutName: Text[250])SetSelectedLayout(LayoutName: Text[250]; AppID: Guid)GetSelectedLayout(): Text[250]GetSelectedAppID(): GuidClearLayoutSelection()
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.
- Table 9651 “Report Layout Selection” (6 calls:
ClearTempLayoutSelected → SetSelectedCustomLayout,ClearTempLayoutSelected → SetSelectedLayout,GetTempLayoutSelected → GetSelectedCustomLayout, …) - Codeunit 44 “ReportManagement” (3 calls:
SelectReportLayoutCode → ClearLayoutSelection,SelectReportLayoutCode → GetSelectedAppID,SelectReportLayoutCode → GetSelectedLayout) - Codeunit 9660 “Report Layouts Impl.” (2 calls:
RunCustomReport → ClearLayoutSelection,RunCustomReport → SetSelectedLayout)
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: "Design-time Report Selection"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.