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

Page 6970 "Exp. Locations Preview"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 2 connected objects and pages

Table 6925 "Expense Location" (relates to)Expense LocationCodeunit 6973 "Create Expense Categories" (calls)Create Expense Categories

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 · captioned “Expense locations” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Expense locations
Extensible false
SourceTable Expense Location
PageType List
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
Group No. No. Specifies the location code.
Description Description Specifies a short description of the location.
Country/Region Code Country/Region Code Specifies the country or region of the location.
Status StatusText Specifies whether the row is a new default that will be added or already exists.

Procedures

1 local procedures, no public ones.

Triggers

OnOpenPage, OnAfterGetRecord

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: "Exp. Locations Preview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources