Page 7103 "Travelers API"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29present
- BC30changed
Neighbourhood 2 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Traveler |
| 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 |
— |
| Travel Request No. | Spend Request No. | Specifies the travel request to which the traveler is added. from the table field | |
| Line No. | Line No. | — | |
| Expense User No. | Expense User No. | Specifies the expense user who is traveling. from the table field | |
| Expense User Name | Expense User Name | Specifies the name of the traveler. from the table field |
Triggers
OnInit
Relations
- source table Table 6938 “Traveler”
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-09-17 #11333 Align travel request APIs with employee travelers and expense report lifecycle (main, BC30, feature)
- 2026-09-09 #11007 Add Travel Request API lifecycle to Expense Agent (main, BC30, feature)
- 2026-08-10 #9391 [Master] - Slice 616928: [Expense Management] [App part] Expense Managements Travel Requisitions 💸 (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: "Travelers API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.