Page 7129 "Travel Request Card"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29present
- BC30changed
Neighbourhood 3 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · captioned “Travel Request” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Travel Request |
| SourceTable | Spend Request |
| PageType | Document |
| 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 number of the travel request. |
| Requested For | Requested For | Specifies the expense user for whom the travel request is being created. | |
| Requested For Name | Requested For Name | Specifies the name of the expense user for whom the travel request is being created. | |
| Purpose | Purpose | Specifies the purpose of the travel request. | |
| Status | Status | Specifies the status of the travel request. | |
| ClosedAt | Closed At | Specifies when the travel request was closed. | |
| ClosedByDoc | Closed By Document No. | Specifies the document that closed the travel request. | |
| Currency Code | Currency Code | Specifies the currency of the travel request. | |
| Total Expected Amount | Total Expected Amount | Specifies the total expected amount of the travel request. | |
| Total Expected Amount (LCY) | Total Expected Amount (LCY) | Specifies the total expected amount of the travel request in local currency. | |
| TotalSpentAmountLCY | Total Spent Amount (LCY) | Specifies the total amount that has been spent against the travel request in local currency. | |
| Remaining Amount (LCY) | Rec.GetRemainingAmountLCY() |
Specifies the difference between estimated amount and actually spent amount. | |
| Shortcut Dimension 1 Code | Shortcut Dimension 1 Code | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up. | |
| Shortcut Dimension 2 Code | Shortcut Dimension 2 Code | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up. | |
| Content | Lines | part Page 7137 “Travel Request Subform” | — |
| Schedule | Expected Start Date | Expected Start Date | Specifies the expected start date of the travel. |
| Expected End Date | Expected End Date | Specifies the expected end date of the travel. | |
| Actual Start Date and Time | Actual Start Date and Time | Specifies the actual start date and time of the travel. | |
| Actual End Date and Time | Actual End Date and Time | Specifies the actual end date and time of the travel. | |
| Travel Details | Business Justification | Business Justification | Specifies the business justification for the travel. |
| International Travel | International Travel | Specifies whether the travel is international. | |
| Origin Country | Origin Country/Region Code | Specifies the origin country for the travel. | |
| Destination Country | Dest. Country/Region Code | Specifies the destination country for the travel. | |
| Restrictions | Restrictions | Specifies any travel restrictions that apply. | |
| Travel Policy Acknowledgment | Travel Policy Acknowledgment | Specifies whether the travel policy has been acknowledged. | |
| Per Diem Included | Per Diem Included | Specifies whether per diem is included in the travel request. | |
| Approval | Approved by User Name | Approved/Rejected by User Name | Specifies the name of the user who approved or rejected the travel request. |
| Approved At | Approved/Rejected At | Specifies when the travel request was approved or rejected. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Release | Release | Set the status field to Released so that it can be processed for approval. | |
| Reopen | Set the status field to Open so that it can be edited. | ||
| Close | Set the status field to Closed so it cannot be used anymore. | ||
| Navigation | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to expenses to distribute costs and analyze transaction history. | |
| Travelers | View the travelers associated with this travel request. | Page 7101 “Travelers” |
Triggers
OnNewRecord
Relations
- source table Table 6840 “Spend Request”
Pages and codeunits on this table
- Page 7136 “Travel Request List” (card page)
Recent changes
- 2026-10-02 #12074 Expense Agent: travel request expense location, per-traveler reports, activity log and submitter comment (main, BC30, feature)
- 2026-09-23 #11595 [Master] Bug 650348: [Expense Agent] Closed travel requests are editable and are missing approver info. (main, BC30, fix)
- 2026-09-23 #11593 [29.x] - Bug 650481[Expense Agent] Closed travel requests are editable and are missing approver info. (releases/29.x, BC29, fix)
- 2026-09-09 #11007 Add Travel Request API lifecycle to Expense Agent (main, BC30, feature)
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: "Travel Request Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.