Page 6949 "Expense User"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Expense User |
| PageType | Card |
| 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 for this expense user. |
| Employee No. | Employee No. | Specifies the value of the Employee No. field. | |
| Resource No. | Resource No. | Specifies the resource linked to the employee. | |
| Name | Name | Specifies the expense user name. | |
| Specifies the expense user’s email address. | |||
| Job Title | Job Title | Specifies the expense user’s job title. | |
| Expense Team Code | Expense Team Code | Specifies the expense team code the expense user belongs to. | |
| Team Manager | Team Manager | Specifies the team manager for this expense user. | |
| Can Approve | Can Approve | Specifies whether the employee can approve expense. from the table field | |
| ApproverNo | Approver No. | Specifies the number of the approver for this expense user. | |
| ApproverName | Approver Name | Specifies the name of the approver for this expense user. | |
| Welcome Email Status | Welcome Email Status | Specifies whether a welcome email has been queued, sent, or failed for the expense user. | |
| Approval Information | Approval Limit (LCY) | Approval Limit (LCY) | Specifies the maximum expense report amount this user can approve. Leave empty when Unlimited Approval is selected. from the table field |
| Unlimited Approval | Unlimited Approval | Specifies that this user can approve expense reports without a maximum amount. from the table field | |
| Content | Can approve for these Expense Users | part Page 6947 “Expense Approval Setups Part” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Create Employee | Checks for an existing employee by email and creates an employee if no match exists. | |
| Send Welcome Email | Sends a welcome email to the expense user. | ||
| Navigation | Approval Setup | Opens the Expense Approval Setup page for this expense user. |
Procedures
2 local procedures, no public ones.
Triggers
OnDeleteRecord, OnQueryClosePage, OnOpenPage, OnAfterGetCurrRecord
Relations
- source table Table 6923 “Expense User”
Pages and codeunits on this table
- Page 6951 “Expense Users” (card page)
- Table 6923 “Expense User” (drill-down page)
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 27 “Confirm Management” (1 call:
OnQueryClosePage → GetResponseOrDefault) - Codeunit 6900 “Expense Doc No Visibility” (1 call:
SetCodeFieldVisible → ExpenseUserNoIsVisible)
Recent changes
- 2026-09-28 #11639 [Master] - Slice 640938: [Expense Agent][VENDOR] Adding approval limits (November ’26) (main, BC30, feature)
- 2026-09-23 #11705 [Master] - Bug 650785: [Expense Agent] Deleting an itemized Expense Category shows misleading missing-subcategories confirmation (main, BC30, fix)
- 2026-09-02 #10807 [29.x][Expense Agent] Confirm before closing Expense User Card without Employee No. (releases/29.x, BC29, fix)
- 2026-09-02 #10638 [Master] [Expense Agent] Bug 639921 Confirm before closing Expense User Card without Employee No. (main, BC30, fix)
- 2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)
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). 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 User"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.