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

Codeunit 6969 "Expense Consumption Handler"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 3 connected objects and pages

Codeunit 7785 "Copilot Quota" (calls, 3 links)Copilot QuotaCodeunit 6968 "Expense Audit Subscribers" (calls, 2 links)Expense Audit SubscribersPage 6968 "Expense User Cons. API" (calls, 2 links)Expense User Cons. API

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
Access Internal
Permissions tabledata “Expense Agent Env. Consumption” = i

Procedures

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

Plus 1 local procedures.

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.

Called by

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: "codeunit", object_name: "Expense Consumption Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources