Page 5617 "FA Locations"
Base Application · Microsoft.FixedAssets.Setup
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.FixedAssets.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | FA Locations |
| SourceTable | FA Location |
| PageType | List |
| UsageCategory | Administration |
| 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 |
|---|---|---|---|
| Control1 | Code | Code | Specifies a location code for the fixed asset. from the table field |
| Name | Name | Specifies the name of the fixed asset location. from the table field |
Relations
- source table Table 5609 “FA Location”
Pages and codeunits on this table
- Table 5609 “FA Location” (lookup page)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
Ask your agent
Procedure bodies are not stored here (D10). 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 Locations"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.