Table 84 "Acc. Schedule Name"

Base Application · Microsoft.Finance.FinancialReports · captioned “Financial Report Row Definition” · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 103 “Account Schedule Names” (10 Learn pages).

Properties

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

Keys

• Key1: Name (clustered)

Trigger event subscribers

• OnAfterDeleteEvent: Codeunit 1351 “Telemetry Subscribers” LogAccScheduleNameLifecycleDelete
• OnAfterInsertEvent: Codeunit 1351 “Telemetry Subscribers” LogAccScheduleNameLifecycleInsert
• OnAfterModifyEvent: Codeunit 1351 “Telemetry Subscribers” LogAccScheduleNameLifecycleModify
• OnAfterRenameEvent: Codeunit 1351 “Telemetry Subscribers” LogAccScheduleNameLifecycleRename

Procedures

• DimTotalingLinesAreEmpty(DimNumber: Integer): Boolean: Checks whether dimension totaling lines are empty for the specified dimension number. Validates if any account schedule lines contain dimension totaling values for the given dimension.
• ClearDimTotalingLines(DimNumber: Integer): Clears dimension totaling values for all account schedule lines for the specified dimension number. Removes dimension totaling filters when analysis view dimensions are changed to maintain data consistency.
• Export(): Exports the account schedule definition to an XML configuration package for deployment and backup purposes. Creates configuration package with account schedule name, lines, and related setup for import/export functionality.
• AddRowDefinitionToConfigPackage(AccScheduleName: Code[10]; var ConfigPackage: Record "Config. Package"; PackageCode: Code[20]): Adds account schedule row definition tables to configuration package for export processing. Includes account schedule name, lines, and related analysis view configuration in the package.
• Import(): Imports account schedule definition from XML configuration package file selected by user. Processes XML import and applies configuration package to create account schedule with lines and settings.
• ApplyPackage(PackageCode: Code[20]): Applies imported configuration package to create account schedule definition with validation and naming. Processes package data, validates account schedule name, and applies configuration to Business Central.
• RenameAccountScheduleInPackage(PackageCode: Code[20]; OldName: Code[10]; NewName: Code[10]): Renames account schedule references within configuration package data to avoid naming conflicts during import. Updates account schedule name and related line references in package data before applying configuration.

Plus 11 local procedures.

Triggers

OnRename, OnDelete

Relations

• lookup page Page 103 “Account Schedule Names”
• Default Column Layout: TableRelation Table 333 “Column Layout Name”
• Analysis View Name: TableRelation Table 363 “Analysis View”
• Status Blocked: CalcFormula Table 8395 “Financial Report Status”
• Status: TableRelation Table 8395 “Financial Report Status”

Referenced by

16 fields in 8 objects relate to this table (TableRelation or CalcFormula).

• Table 98 “General Ledger Setup”: Acc. Sched. for Balance Sheet, Acc. Sched. for Cash Flow Stmt, Acc. Sched. for Income Stmt., Acc. Sched. for Retained Earn., Fin. Rep. Bal. Sheet Row, Fin. Rep. Cash Flow Stmt. Row, Fin. Rep. Income Stmt. Row, Fin. Rep. Retained Earn. Row
• Table 136 “Acc. Sched. KPI Web Srv. Line”: Acc. Schedule Description, Acc. Schedule Name
• Table 1312 “Trial Balance Setup”: Account Schedule Name
• Table 762 “Account Schedules Chart Setup”: Account Schedule Name
• Table 763 “Acc. Sched. Chart Setup Line”: Account Schedule Name
• Table 8360 “Financial Report Schedule”: Financial Report Row Group
• Table 85 “Acc. Schedule Line”: Schedule Name
• Table 88 “Financial Report”: Financial Report Row Group

Pages and codeunits on this table

• Page 103 “Account Schedule Names” (source 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.

• Codeunit 8614 “Config. XML Exchange” (3 calls: Export → ExportPackage, Import → GetImportedPackageCode, Import → ImportPackageXMLFromClient)
• Codeunit 457 “Environment Information” (1 call: LogImportExportTelemetry → IsSaaS)
• Codeunit 8611 “Config. Package Management” (1 call: ApplyPackage → ApplyPackage)
• Codeunit 8703 “Feature Telemetry” (1 call: LogImportExportTelemetry → LogUsage)

Recent changes

• 2026-10-05 #12213 [Financial Reports] Add row and column definition preview (main, BC30, feature)
• 2026-09-21 #11517 [29.x]-export/import of a report definition fails if the statuses in the originating company do not exist in the destination company (releases/29.x, BC29, fix)
• 2026-08-31 #10604 [Main]-export/import of a report definition fails if the statuses in the originating company do not exist in the destination company (main, BC30, fix)

Countries that replace it

CA, ES, MX, RU, US

Deprecations

• field Default Column Layout: Removed 25.0 (#if not CLEANSCHEMA25), “Use now the Column Group property in the table Financial Report”

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: "table", object_name: "Acc. Schedule Name"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.