Page 6968 "Expense User Cons. API"

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

Properties

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).

Procedures

• LogAIConsumption(CopilotQuotaUsageAmount: Integer; CopilotQuotaUsageType: Enum "Copilot Quota Usage Type"; ActionsSummary: Text[1024]; ActionsDescription: Text; ConsumptionSourceType: Enum "Expense Agent Cons. Source"; ConsumptionSourceSystemId: Guid; ConsumptionSourceOperationName: Code[50]): Text[1024]
• CanConsume(): Boolean

Triggers

OnInit

Relations

• source table Table 6923 “Expense User”

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 6993 “Expense Agent API Validation” (3 calls: CanConsume → VerifyAgentAccess, LogAIConsumption → VerifyAgentAccess, OnInit → VerifyAgentAccess)
• Codeunit 6969 “Expense Consumption Handler” (2 calls: CanConsume → CanConsume, LogAIConsumption → LogAIConsumption)

Recent changes

• 2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)

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