Page 7131 "Mileage Rate Setup API"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Mileage Rate Setup |
| PageType | API |
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 | Id | Rec.SystemId |
— |
| Code | Code | Specifies the unique code that identifies the mileage rate. from the table field | |
| Vehicle Type | Vehicle Type | Specifies the vehicle type this mileage rate applies to. Leave blank to define a generic rate that is used when no rate matches the vehicle type on the expense. from the table field | |
| Starting Date | Starting Date | Specifies the first date the mileage rate is effective. from the table field | |
| Ending Date | Ending Date | Specifies the last date the mileage rate is effective. Leave blank for an open-ended rate. from the table field | |
| Rate | Rate | Specifies the reimbursement amount per unit of distance for this mileage rate. from the table field | |
| Currency Code | Currency Code | Specifies the currency the mileage rate is expressed in. Leave blank to use the local currency. from the table field |
Triggers
OnInit
Relations
- source table Table 6939 “Mileage Rate Setup”
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 6993 “Expense Agent API Validation” (1 call:
OnInit → VerifyAgentAccess)
Recent changes
- 2026-08-27 #10561 Mileage Rate Setup (main, BC30, feature, added)
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: "Mileage Rate Setup API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.