Table 6938 "Traveler"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29present
- BC30changed
Neighbourhood 5 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 7101 “Travelers” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Traveler |
| Access | Internal |
| DataClassification | CustomerContent |
| LookupPageId | Travelers |
| DrillDownPageId | Travelers |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Spend Request No. | Code[20] | Specifies the travel request to which the traveler is added. | TableRelation Table 6840 “Spend Request” (Spend Request) |
| 3 | Line No. | Integer | — | |
| 4 | Expense User No. | Code[20] | Specifies the expense user who is traveling. | TableRelation Table 6923 “Expense User” (“Expense User”.“No.”); NotBlank |
| 5 | Expense User Name | Text[100] | Specifies the name of the traveler. |
Keys
- PK: Spend Request No., Line No. (clustered)
Procedures
2 local procedures, no public ones.
Triggers
OnInsert, OnDelete
Relations
- drill-down page Page 7101 “Travelers”
- lookup page Page 7101 “Travelers”
- Spend Request No.: TableRelation Table 6840 “Spend Request”
- Expense User No.: TableRelation Table 6923 “Expense User”
Pages and codeunits on this table
- Page 7101 “Travelers” (source table)
- Page 7103 “Travelers API” (source table)
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-17 #11333 Align travel request APIs with employee travelers and expense report lifecycle (main, BC30, feature)
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: "table", object_name: "Traveler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.