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

Table 6908 "Expense Report Line Particip."

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 8 connected objects and pages

Table 6906 "Expense Report Header" (relates to)Expense Report HeaderTable 6907 "Expense Report Line" (relates to)Expense Report LineTable 6921 "Expense Category" (relates to)Expense CategoryTable 6929 "Expense Subcategory" (relates to)Expense SubcategoryTable 9 "Country/Region" (relates to)Country/RegionPage 6912 "Expense Report Line Particips" (pages and codeunits on it, 2 links)Expense Report Line ParticipsPage 6909 "Exp. Report Line Particip. API" (pages and codeunits on it)Exp. Report Line Particip. APICodeunit 6910 "Expense Report" (calls)Expense Report

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 Report Line Participants” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Expense Report Line Participants
Access Internal
DataClassification CustomerContent
LookupPageId Expense Report Line Particips

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 Report No. Code[20] — TableRelation Table 6906 “Expense Report Header” (“Expense Report Header”.“No.”)
2 Expense Report Line No. Integer — TableRelation Table 6907 “Expense Report Line” (“Expense Report Line”.“Line No.” where(“Document No.” = field(“Expense Report No.”)))
3 Line No. Integer —
5 Expense No. Code[20] — TableRelation Expense.“No.”
6 Expense Category Code Code[20] — TableRelation Table 6921 “Expense Category” (“Expense Category”.Code where(Inactive = const(false)))
7 Expense Subcategory Code Code[20] — TableRelation Table 6929 “Expense Subcategory” (“Expense SubCategory”.Code where(“Expense Category Code” = field(“Expense Category Code”), Inactive = const(false)))
8 Participant Type Enum “Expense Participant Type” Specifies the type of participant (Employee, Customer, Vendor, Other). via Page 6912 “Expense Report Line Particips” enum Enum 6986 “Expense Participant Type”
9 Participant Employee No. Code[20] Specifies the employee number if the participant is an employee. via Page 6912 “Expense Report Line Particips” TableRelation if (“Participant Type” = const(Employee)) Employee.“No.”
10 Participant Name Text[100] Specifies the name of the participant. via Page 6912 “Expense Report Line Particips”
11 Participant Organization Text[100] Specifies the organization of the participant. via Page 6912 “Expense Report Line Particips”
12 Participant Country/Region Code[10] Specifies the country/region of the participant. via Page 6912 “Expense Report Line Particips” TableRelation Table 9 “Country/Region” (“Country/Region”.Code)
13 Participant Title Text[30] Specifies the job title of the participant. via Page 6912 “Expense Report Line Particips”
14 Participant Email Text[80] Specifies the email address of the participant. via Page 6912 “Expense Report Line Particips”

Keys

  • PK: Expense Report No., Expense Report Line No., Line No. (clustered)

Procedures

6 local procedures, no public ones.

Triggers

OnInsert, OnModify, OnDelete

Relations

Pages and codeunits on this table

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: "table", object_name: "Expense Report Line Particip."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources