BC Observatoryunofficial, made by waldo
pageFinanceofficial - Microsoftderived - from the source, no model text

Page 103 "Account Schedule Names"

Base Application · Microsoft.Finance.FinancialReports

Open in Claude103.mdSource on GitHub

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC28declaration changed
  5. BC29-30unchanged

Neighbourhood 13 connected objects and pages

Table 84 "Acc. Schedule Name" (relates to)Acc. Schedule NameTable 84 "Acc. Schedule Name" (pages and codeunits on it)Acc. Schedule NameCodeunit 18 "Financial Report Mgt." (calls)Financial Report Mgt.Audit changes to your setup (Learn pages)Audit changes to your setupAuditing and financial reporting (Learn pages)Auditing and financial repor…Build financial reports using financial data and account categories (Learn pages)Build financial reports usin…Column definitions in Financial Reporting (Learn pages)Column definitions in Financ…Financial analytics (Learn pages)Financial analyticsFinancial Reporting FAQ (Learn pages)Financial Reporting FAQMake cash flow forecasts using financial reports (Learn pages)Make cash flow forecasts usi…Row definitions in Financial Reporting (Learn pages)Row definitions in Financial…Set Up and Publish KPI Web Services Based on Financial Reports (Learn pages)Set Up and Publish KPI Web S…Troubleshoot Financial Reporting (Learn pages)Troubleshoot Financial Repor…

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.Finance.FinancialReports · captioned “(Financial Report) Row Definitions” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption (Financial Report) Row Definitions
SourceTable Acc. Schedule Name
PageType List
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

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 Name Name Specifies the unique name (code) of the financial report row definition. You can use up to 10 characters. from the table field
Description Description Specifies a description of the financial report row definition. The description is not shown on the final report but is used to provide more context when using the definition. from the table field
Analysis View Name Analysis View Name Specifies the name of the analysis view you want the row definition to use. This field is optional. from the table field
Status Status Specifies the status code for the row definition. The status code helps you organize the lifecycle of your row definitions. from the table field
Internal Description Internal Description Specifies the internal description of row definition. The internal description is not shown on the final report but is used to provide more context when using the definition. from the table field

Actions

Group Action ToolTip Runs
Processing Edit Row Definition Change the row definition based on the current row definition.
Where-Used View or edit financial reports in which the row definition is used.
Copy Row Definition Create a copy of the current row definition.
Import Row Definition Import a RapidStart configuration package that contains settings for a set of row definitions. Importing row definitions lets you share them, for example, with another business unit. This requires that the row definition has been exported.
Export Row Definition Export settings for the selected row definition to a RapidStart configuration package. Exporting a row definition lets you share it with another business unit.

Triggers

OnOpenPage, OnNewRecord

Relations

Pages and codeunits on this table

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: "Account Schedule Names"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 8 of 11 sources

Show 3 more