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

Table 6932 "Expense Approval Setup"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 8 connected objects and pages

Table 6923 "Expense User" (relates to, 4 links)Expense UserPage 6939 "Expense Approval Setup" (pages and codeunits on it, 3 links)Expense Approval SetupPage 6947 "Expense Approval Setups Part" (pages and codeunits on it)Expense Approval Setups PartPage 6955 "Expense Approval Setup API" (pages and codeunits on it)Expense Approval Setup APICodeunit 6968 "Expense Audit Subscribers" (event subscribers, 4 links)Expense Audit SubscribersTable 6923 "Expense User" (referenced by)Expense UserReview 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

Learn documents this table through its pages: Page 6939 “Expense Approval Setup” (2 Learn pages).

Properties

Property Value
Caption Expense Approval Setup
Access Internal
DataClassification CustomerContent
LookupPageId Expense Approval Setup
DrillDownPageId Expense Approval Setup

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 Expense User No. Code[20] Specifies the number of the expense user for expense approval setup. via Page 6939 “Expense Approval Setup” TableRelation Table 6923 “Expense User” (“Expense User”.“No.”)
2 Entra Id Guid Specifies the Entra Id for expense approval setup. via Page 6939 “Expense Approval Setup”
3 Approver No. Code[20] Specifies the number of the approver for expense approval setup. via Page 6939 “Expense Approval Setup” TableRelation Table 6923 “Expense User” (“Expense User”.“No.” where(“Can Approve” = const(true)))
4 Expense User Name Text[100] Specifies the name of the expense user. FlowField: lookup(“Expense User”.Name where(“No.” = field(“Expense User No.”))); not editable
5 Approver Name Text[100] Specifies the name of the approver. FlowField: lookup(“Expense User”.Name where(“No.” = field(“Approver No.”))); not editable

Keys

  • Key1: Expense User No. (clustered)
  • ApproverNo: Approver No.

Trigger event subscribers

Procedures

2 local procedures, no public ones.

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

Recent changes

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

Evidence 1 sources