Page extension 6900 "Exp. Project Ledg. Entries"
ExpenseAgent · Microsoft.ExpenseAgent
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
ExpenseAgent · Microsoft.ExpenseAgent · BC29-30 · source at ea08af5e · facts from BC29
Extends Job Ledger Entries.
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 |
|---|---|---|---|
| addafter(Location Code) | Expense Report No. | Expense Report No. | Specifies the number of the posted expense report associated with this project ledger entry. from the table field |
| Expense Report Line No. | Expense Report Line No. | Specifies the line number of the posted expense report associated with this project ledger entry. from the table field |
Relations
- extends Page 92 “Job Ledger Entries”
Recent changes
- 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: "pageextension", object_name: "Exp. Project Ledg. Entries"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.