Page 4760 "FA Module Setup"
ContosoCoffeeDemoDataset · Microsoft.DemoData.FixedAsset
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoData.FixedAsset · captioned “Fixed Assets Module Setup” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Fixed Assets Module Setup |
| Extensible | false |
| SourceTable | FA Module Setup |
| PageType | Card |
| ApplicationArea | FixedAssets |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Setup Data | Default Depr. Book | Default Depreciation Book | Specifies the default depreciation book to use for the scenarios. |
Triggers
OnOpenPage
Relations
- source table Table 4767 “FA Module Setup”
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 4774 “FA Module” (1 call:
RunConfigurationPage → (object))
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: "page", object_name: "FA Module Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.