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

Table 7108 "Expense Vehicle Type"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 7 connected objects and pages

Page 7130 "Expense Vehicle Types" (pages and codeunits on it, 3 links)Expense Vehicle TypesPage 7107 "Expense Vehicle Type API" (pages and codeunits on it)Expense Vehicle Type APITable 6900 "Expense" (referenced by)ExpenseTable 6907 "Expense Report Line" (referenced by)Expense Report LineTable 6916 "Posted Expense Report Line" (referenced by)Posted Expense Report LineTable 6939 "Mileage Rate Setup" (referenced by)Mileage Rate SetupSet Up Mileage Rates for Expense Management (Learn pages)Set Up Mileage Rates for Exp…

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 “Vehicle Type” · BC29-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 7130 “Expense Vehicle Types” (1 Learn page).

Properties

Property Value
Caption Vehicle Type
Access Internal
DataClassification CustomerContent
LookupPageId Expense Vehicle Types
DrillDownPageId Expense Vehicle Types

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 Code Code[20] Specifies the unique code that identifies the vehicle type. NotBlank
2 Description Text[100] Specifies a description of the vehicle type.

Keys

  • PK: Code (clustered)

Relations

Referenced by

4 fields in 4 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 Vehicle Type"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources