Page 1818 "Cash Flow Forecast Wizard"
Base Application · Microsoft.CashFlow.Forecast
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.CashFlow.Forecast · captioned “Set Up Cash Flow Forecast” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Set Up Cash Flow Forecast |
| PageType | NavigatePage |
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 |
|---|---|---|---|
| Control6 | MediaResourcesStandard.““Media Reference”” | MediaResourcesStandard."Media Reference" |
— |
| Control8 | MediaResourcesDone.““Media Reference”” | MediaResourcesDone."Media Reference" |
— |
| Control22 | LiquidFundsGLAccountFilter | LiquidFundsGLAccountFilter |
— |
| Control15 | UpdateFrequency | UpdateFrequency |
— |
| Azure AI forecasts can help you anticipate and proactively address upcoming cash flow needs. If you are using Dynamics 365 Business Central, Azure Machine Learning credentials are set automatically. | Enable Azure AI | AzureAIEnabled |
— |
| If you have your own Machine Learning service, enter the API URL and API key for the service and use that instead. | API URL | APIURL |
— |
| API Key | APIKEY |
— | |
| Control31 | TaxablePeriod | TaxablePeriod |
— |
| Control29 | TaxPaymentWindow | TaxPaymentWindow |
— |
| Control25 | DummyCashFlowSetup.““Tax Bal. Account Type”” | DummyCashFlowSetup."Tax Bal. Account Type" |
— |
| Control23 | DummyCashFlowSetup.““Tax Bal. Account No.”” | DummyCashFlowSetup."Tax Bal. Account No." |
— |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Back | — | |
| Next | — | ||
| Finish | — |
Procedures
12 local procedures, no public ones.
Triggers
OnInit, OnOpenPage, OnQueryClosePage
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 841 “Cash Flow Management” (3 calls:
FinishAction → SetupCashFlow,FinishAction → UpdateCashFlowForecast,GetLiquidFundsGLAccountFilter → GetCashAccountFilter) - Codeunit 1990 “Guided Experience” (2 calls:
FinishAction → CompleteAssistedSetup,OnQueryClosePage → AssistedSetupExistsAndIsNotComplete) - Codeunit 4030 “Client Type Management” (1 call:
LoadTopBanners → GetCurrentClientType) - Codeunit 457 “Environment Information” (1 call:
OnSaaS → IsSaaS)
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: "Cash Flow Forecast Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.