Page 867 "CF Availability by Periods"
Base Application · Microsoft.CashFlow.Forecast
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.CashFlow.Forecast · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | CF Availability by Periods |
| SourceTable | Cash Flow Forecast |
| PageType | ListPlus |
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 |
|---|---|---|---|
| Options | No. | No. | Specifies the number of the involved entry or record, according to the specified number series. |
| Manual Payments From | Manual Payments From | Specifies a starting date from which manual payments should be included in cash flow forecast. | |
| To | Manual Payments To | Specifies a starting date to which manual payments should be included in cash flow forecast. | |
| Liquid Funds | LiquidFunds |
Specifies if the cash flow forecast must include liquid funds in the general ledger. | |
| Creation Date | Creation Date | Specifies the date that the forecast was created. | |
| Rounding Factor | RoundingFactor |
Specifies the factor that is used to round the amounts. | |
| View by | PeriodType |
Specifies by which period amounts are displayed. | |
| View as | AmountType |
Specifies how amounts are displayed. Net Change: The net change in the balance for the selected period. Balance at Date: The balance as of the last day in the selected period. | |
| Content | CFAvailabLines | part Page 866 “Cash Flow Availability Lines” | — |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 840 “Cash Flow Forecast”
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.
- Codeunit 9200 “Matrix Management” (1 call:
UpdateSubForm → RoundAmount)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "CF Availability by Periods"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.