pageAL Developmentofficial - Microsoftderived - from the source, no model text

Page 863 "CF Entries Dim. Matrix"

Base Application · Microsoft.CashFlow.Forecast

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 847 "Cash Flow Forecast Entry" (relates to)Cash Flow Forecast EntryPage 560 "Dimension Value List" (calls)Dimension Value ListAnalyze cash flows (Learn pages)Analyze cash flows

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.

Base Application · Microsoft.CashFlow.Forecast · captioned “CF Forcst. Entries Dim. Overv. M.” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption CF Forcst. Entries Dim. Overv. M.
SourceTable Cash Flow Forecast Entry
PageType List

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
Control1 Cash Flow Date Cash Flow Date Specifies the cash flow date that the entry is posted to.
Document No. Document No. Specifies the document that represents the forecast entry.
Cash Flow Forecast No. Cash Flow Forecast No. Specifies a number for the cash flow forecast.
Cash Flow Account No. Cash Flow Account No. Specifies the number of the cash flow account that the forecast entry is posted to.
Description Description Specifies a description of the cash flow forecast.
Amount (LCY) Amount (LCY) Specifies the amount of the worksheet line in LCY. Revenues are entered without a plus or minus sign. Expenses are entered with a minus sign.
Entry No. Entry No. Specifies the number of the entry, as assigned from the specified number series when the entry was created.
Field1 MATRIX_CellData[1] —
Field2 MATRIX_CellData[2] —
Field3 MATRIX_CellData[3] —
Field4 MATRIX_CellData[4] —
Field5 MATRIX_CellData[5] —
Field6 MATRIX_CellData[6] —
Field7 MATRIX_CellData[7] —
Field8 MATRIX_CellData[8] —
Field9 MATRIX_CellData[9] —
Field10 MATRIX_CellData[10] —
Field11 MATRIX_CellData[11] —
Field12 MATRIX_CellData[12] —
Field13 MATRIX_CellData[13] —
Field14 MATRIX_CellData[14] —
Field15 MATRIX_CellData[15] —
Field16 MATRIX_CellData[16] —
Field17 MATRIX_CellData[17] —
Field18 MATRIX_CellData[18] —
Field19 MATRIX_CellData[19] —
Field20 MATRIX_CellData[20] —
Field21 MATRIX_CellData[21] —
Field22 MATRIX_CellData[22] —
Field23 MATRIX_CellData[23] —
Field24 MATRIX_CellData[24] —
Field25 MATRIX_CellData[25] —
Field26 MATRIX_CellData[26] —
Field27 MATRIX_CellData[27] —
Field28 MATRIX_CellData[28] —
Field29 MATRIX_CellData[29] —
Field30 MATRIX_CellData[30] —
Field31 MATRIX_CellData[31] —
Field32 MATRIX_CellData[32] —

Actions

Group Action ToolTip Runs
Entries Dimensions View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.

Procedures

  • Load(NewMATRIX_Captions: array[32] of Text[80]; PKFirstCaptionInSet: Text; LengthOfCurrSet: Integer)
  • SetTempCFForecastEntry(var NewCFForecastEntry: Record "Cash Flow Forecast Entry")
  • SetColumnVisibility()

Plus 6 local procedures.

Triggers

OnAfterGetRecord, OnFindRecord, OnInit, OnNextRecord, OnOpenPage

Relations

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.

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

Evidence 2 sources