---
id: object/table/333
type: object
title: Table 333 "Column Layout Name"
summary: Table 333 "Column Layout Name" in Base Application (Microsoft.Finance.FinancialReports). 6 fields, 2 public procedures. Present since at least BC23, still in BC30, changed in BC24-26, BC28, BC30.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "30"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: d7288a5a2905cadbb1da44ebf8ce4a74e874c107e4a1e3198b865d60eae8ca2c
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Finance/FinancialReports/ColumnLayoutName.Table.al
    title: src/Layers/W1/BaseApp/Finance/FinancialReports/ColumnLayoutName.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/across-setup-auditing
    - https://learn.microsoft.com/dynamics365/business-central/bi-column-definitions
    - https://learn.microsoft.com/dynamics365/business-central/bi-how-work-account-schedule
    - https://learn.microsoft.com/dynamics365/business-central/finance-financial-reporting-auditing
    - https://learn.microsoft.com/dynamics365/business-central/finance-financial-reporting-faq
    - https://learn.microsoft.com/dynamics365/business-central/walkthrough-making-cash-flow-forecasts-by-using-account-schedules
  objects: []
  features: []
  topics:
    - topic/business-central/analytics-business-intelligence-and-repo/built-in-reports/finance
    - topic/business-central/analytics-business-intelligence-and-repo/kpis-dashboards-and-financial-reports
    - topic/business-central/business-functionality/finance/financial-analytics/financial-reporting
    - topic/business-central/business-functionality/finance/manage-cash-flow
    - topic/business-central/business-functionality/set-up-business-central
    - topic/business-central/business-functionality/set-up-business-central/set-up-finance
    - topic/business-central/get-started/learn/business-process-walkthroughs
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes:
    - change/bcapps/12213
object_type: table
object_id: 333
name: Column Layout Name
caption: Financial Report Column Definition
namespace: Microsoft.Finance.FinancialReports
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
  - "25"
  - "26"
  - "28"
  - "30"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 6
  procedures: 7
  events: 0
  subscribers: 0
relations:
  out: 4
  referenced_by: 9
  pages: 1
  extended_by: 0
  event_subscribers: 4
  calls: 5
  called_by: 0
  implements: 0
---

# Table 333 "Column Layout Name"

> Table 333 "Column Layout Name" in Base Application (Microsoft.Finance.FinancialReports). 6 fields, 2 public procedures. Present since at least BC23, still in BC30, changed in BC24-26, BC28, BC30.

Base Application · Microsoft.Finance.FinancialReports · captioned "Financial Report Column Definition" · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Finance/FinancialReports/ColumnLayoutName.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 488 "Column Layout Names"](../page/488.md) (6 Learn pages).

## Properties

| Property | Value |
|---|---|
| Caption | Financial Report Column Definition |
| DataClassification | CustomerContent |

## 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.

| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Name | Code[10] | Specifies the unique name (code) of the financial report column definition. You can use up to 10 characters. | NotBlank |
| 2 | Description | Text[80] | Specifies a description of the financial report columns definition. The description is not shown on the final report but is used to provide more context when using the definition. |  |
| 4 | Analysis View Name | Code[10] | Specifies the name of the analysis view you want the column definition to use. This field is optional. | TableRelation [Table 363 "Analysis View"](../table/363.md) (Analysis View) |
| 5 | Internal Description | Text[500] | Specifies the internal description of the column definition. The internal description is not shown on the final report but is used to provide more context when using the definition. |  |
| 6 | Status | Code[10] | Specifies the status code for the column definition. The status code helps you organize the lifecycle of your column definitions. | TableRelation [Table 8395 "Financial Report Status"](../table/8395.md) (Financial Report Status) |
| 7 | Status Blocked | Boolean | Specifies the status code is a blocked status. | FlowField: exist("Financial Report Status" where("Code" = field(Status), "Blocked" = const(true))); not editable |

## Keys

- Key1: Name (clustered)

## Trigger event subscribers

- OnAfterDeleteEvent: [Codeunit 1351 "Telemetry Subscribers"](../codeunit/1351.md) LogColumnLayoutNameLifecycleDelete
- OnAfterInsertEvent: [Codeunit 1351 "Telemetry Subscribers"](../codeunit/1351.md) LogColumnLayoutNameLifecycleInsert
- OnAfterModifyEvent: [Codeunit 1351 "Telemetry Subscribers"](../codeunit/1351.md) LogColumnLayoutNameLifecycleModify
- OnAfterRenameEvent: [Codeunit 1351 "Telemetry Subscribers"](../codeunit/1351.md) LogColumnLayoutNameLifecycleRename

## Procedures

- `XMLExchangeExport()`: Exports column layout definition and related columns to XML format for template sharing and backup. Creates configuration package containing column layout name and all associated column layout lines.
- `XMLExchangeImport()`: Imports column layout definition from XML file and applies configuration to create new column layouts. Validates imported package structure and creates column layout name with associated column lines.

Plus 5 local procedures.

## Triggers

OnRename, OnDelete

## Relations

- lookup page [Page 488 "Column Layout Names"](../page/488.md)
- Analysis View Name: TableRelation [Table 363 "Analysis View"](../table/363.md)
- Status Blocked: CalcFormula [Table 8395 "Financial Report Status"](../table/8395.md)
- Status: TableRelation [Table 8395 "Financial Report Status"](../table/8395.md)

## Referenced by

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

- [Table 98 "General Ledger Setup"](../table/98.md): Fin. Rep. Bal. Sheet Column, Fin. Rep. Net Change Column
- [Table 1312 "Trial Balance Setup"](../table/1312.md): Column Layout Name
- [Table 334 "Column Layout"](../table/334.md): Column Layout Name
- [Table 762 "Account Schedules Chart Setup"](../table/762.md): Column Layout Name
- [Table 763 "Acc. Sched. Chart Setup Line"](../table/763.md): Column Layout Name
- [Table 8360 "Financial Report Schedule"](../table/8360.md): Financial Report Column Group
- [Table 84 "Acc. Schedule Name"](../table/84.md): Default Column Layout
- [Table 88 "Financial Report"](../table/88.md): Financial Report Column Group

## Pages and codeunits on this table

- [Page 488 "Column Layout Names"](../page/488.md) (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 8611 "Config. Package Management"](../codeunit/8611.md) (4 calls: `AddColumnDefinitionToPackage → InsertPackage`, `AddColumnDefinitionToPackage → InsertPackageFilter`, `AddColumnDefinitionToPackage → InsertPackageTable`, …)
- [Codeunit 8614 "Config. XML Exchange"](../codeunit/8614.md) (3 calls: `XMLExchangeExport → ExportPackage`, `XMLExchangeImport → GetImportedPackageCode`, `XMLExchangeImport → ImportPackageXMLFromClient`)
- [Codeunit 18 "Financial Report Mgt."](../codeunit/18.md) (1 call: `GetNewColumnDefinitionName → RenameColumnLayoutInPackage`)
- [Codeunit 457 "Environment Information"](../codeunit/457.md) (1 call: `LogImportExportTelemetry → IsSaaS`)
- [Codeunit 8703 "Feature Telemetry"](../codeunit/8703.md) (1 call: `LogImportExportTelemetry → LogUsage`)

## Recent changes

- 2026-10-05 [#12213 [Financial Reports] Add row and column definition preview](../../changes/bcapps/12213.md) (main, BC30, feature)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24-26, BC28, BC30

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: "Column Layout Name")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.
