Page 6935 "Expense Itemizations 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 | Expense Itemization |
| 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 |
— |
| Expense Report No. | Expense No. | — | |
| Expense Category Code | Expense Category Code | — | |
| Expense Subcategory Code | Expense Subcategory Code | — | |
| Description | Description | — | |
| Quantity | Quantity | — | |
| Daily Rate | Daily Rate | — | |
| Amount | Amount | — | |
| Start Date | Start Date | — | |
| Refundable | Refundable | — |
Procedures
ValidateExpenseRule(var ActionContext: WebServiceActionContext)ApplyExpenseRule(var ActionContext: WebServiceActionContext)
Triggers
OnInit
Relations
- source table Table 6902 “Expense Itemization”
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-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (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: "Expense Itemizations API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.