Codeunit 5409 "Feature - Report Selection"
Base Application · System.Environment.Configuration
Across versions
- BC23present
- BC241 procedures changed, 1 procedures added
- BC25-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Tenant Report Layout |
| Permissions | TableData “Feature Data Update Status” = rm |
Procedures
IsDataUpdateRequired(): BooleanReviewData()AfterUpdate(FeatureDataUpdateStatus: Record "Feature Data Update Status")UpdateData(FeatureDataUpdateStatus: Record "Feature Data Update Status")GetTaskDescription(): TextMigrateCustomReportLayouts()Δ BC24 + BC24MigrateCustomReportLayouts(var CustomReportLayout: Record "Custom Report Layout")Δ BC24 + BC24
Plus 2 local procedures.
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 2614 “Feature Data Update Mgt.” (1 call:
UpdateData → LogTask)
Implements
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: "Feature - Report Selection"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.