Page 6920 "Expense Location Card"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 4 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Expense Location Card |
| SourceTable | Expense Location |
| PageType | Card |
| ApplicationArea | Basic, Suite |
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 |
|---|---|---|---|
| General | No. | No. | Specifies the location number. |
| Description | Description | Specifies the description of the expense location. Used for per-diem calculations. | |
| Country/Region Code | Country/Region Code | Specifies the country/region code for the expense location. | |
| City | City | Specifies the city for the expense location. This field is optional and used only when multiple locations exist in the same country/region. | |
| County | County | Specifies the county for the expense location. This field is optional and used this field to further identify or categorize the location within the country/region. |
Relations
- source table Table 6925 “Expense Location”
Pages and codeunits on this table
- Page 6937 “Expense Locations” (card page)
- Table 6925 “Expense Location” (drill-down page)
Recent changes
- 2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)
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: "Expense Location Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.