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

Table 6910 "Expense Report Rule Violation"

ExpenseAgent · Microsoft.ExpenseAgent

Across versions

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

Neighbourhood 5 connected objects and pages

Table 6906 "Expense Report Header" (relates to)Expense Report HeaderPage 6932 "Expense Report Rule Violations" (pages and codeunits on it)Expense Report Rule ViolationsPage 6964 "Exp. Rep. Rule Violations API" (pages and codeunits on it)Exp. Rep. Rule Violations APICodeunit 9500 "Sequence No. Mgt." (calls)Sequence No. Mgt.Table 6907 "Expense Report Line" (referenced by)Expense Report Line

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
DataClassification CustomerContent

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 Report Line No. Integer —
3 Line No. Integer —
4 Description Text[500] Specifies the description of the rule violation. via Page 6932 “Expense Report Rule Violations”

Keys

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

Procedures

  • ClearRuleViolations(ExpenseReportNo: Code[20]; ReportLineNo: Integer)
  • AddRuleViolation(ExpenseReportNo: Code[20]; ReportLineNo: Integer; Violation: Text[500])

Plus 1 local procedures.

Triggers

OnInsert

Relations

Referenced by

1 fields in 1 objects relate to this table (TableRelation or CalcFormula).

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

Evidence 1 sources