pageCopilot & Agentsofficial - Microsoftderived - from the source, no model text

Page 6918 "Expense Users API"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Table 6923 "Expense User" (relates to)Expense UserCodeunit 6993 "Expense Agent API Validation" (calls)Expense Agent API Validation

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
SourceTable Expense User
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 —
Number No. —
Employee Number Employee No. —
Name Name —
Email E-mail —
Job Title Job Title —
Can Approve Can Approve Specifies whether the employee can approve expense. from the table field
Employee Status Employee Status Specifies the employment status of the related employee. from the table field
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
employees part Page 6917 “Employees API” —
expenses part Page 6927 “Expenses API” —
expenseReports part Page 6928 “Expense Reports API” —
activityHistory part Page 7122 “Expense Activity Log API” —
approverView part Page 6969 “Approver View API” —
expenseApprovalSetup part Page 6955 “Expense Approval Setup API” —
projects part Page 7092 “Expense Projects API” —

Triggers

OnInit, OnOpenPage

Relations

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.

Recent changes

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 Users API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources