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

Page 6939 "Expense Approval Setup"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 5 connected objects and pages

Table 6932 "Expense Approval Setup" (relates to)Expense Approval SetupTable 6932 "Expense Approval Setup" (pages and codeunits on it, 2 links)Expense Approval SetupCodeunit 6909 "Expense Approval Helper" (calls)Expense Approval HelperReview and Approve Expense Reports (Learn pages)Review and Approve Expense R…Set Up Expense Users and Teams (Learn pages)Set Up Expense Users and Teams

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 Approval Setup
PageType List
UsageCategory Administration
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
GroupName Expense User No. Expense User No. Specifies the number of the expense user for expense approval setup.
ExpenseUserName Expense User Name Specifies the name of the expense user. from the table field
Entra Id Entra Id Specifies the Entra Id for expense approval setup.
Approver No. Approver No. Specifies the number of the approver for expense approval setup.
ApproverName Approver Name Specifies the name of the approver. from the table field

Relations

Pages and codeunits on this table

Called by

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

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

Evidence 3 sources