Table 6926 "Expense Rule Condition"

ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Expense Rule Condition
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 Category Code	Code[20]	—	TableRelation Table 6921 “Expense Category” (Expense Category)
2	Expense Location	Code[20]	—	TableRelation Table 6925 “Expense Location” (Expense Location)
3	Effective Date	Date	—
4	Line No.	Integer	—
10	Condition Type	Enum “Expense Rule Condition Type”	Specifies the type of rule condition. via Page 6902 “Expense Rule Conditions”	enum Enum 6911 “Expense Rule Condition Type”
20	Value	Decimal	Specifies the maximum amount for this condition (if applicable). via Page 6902 “Expense Rule Conditions”

Keys

PK: Expense Category Code, Expense Location, Effective Date, Line No. (clustered)

Procedures

3 local procedures, no public ones.

Triggers

OnRename

Relations

Expense Category Code: TableRelation Table 6921 “Expense Category”
Expense Location: TableRelation Table 6925 “Expense Location”

Pages and codeunits on this table

Page 6902 “Expense Rule Conditions” (source table)
Page 6922 “Expense Rule Conditions API” (source table)
Page 6965 “Exp. Rule Conditions Preview” (source table)
Codeunit 7126 “Create Expense Rule Conditions” (codeunit runs on it)

Recent changes

2026-09-15 #11425 Bug 650137: [29.x] Expense Locations and Per-diem rules in configuration - Backport (releases/29.x, BC29, feature)
2026-09-10 #10155 Slice 641293: [Expense Agent] Expense Locations and Per-diem rules in configurationAdded more locations (main, BC30, feature)
2026-08-04 #9859 [Master] - Move Expense Agent (Preview) app into BCApps (main, BC30, feature, added)

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