# Report.Language([Integer]) Method
> Version: _Available or changed with runtime version 1.0._
Gets or sets the current language setting for the report.
## Syntax
```al
[CurrentLanguage := ]  Report.Language([Language: Integer])
```
> NOTE
> This method can be invoked using property access syntax.
## Parameters
Report
Type: report-data-type
An instance of the report-data-type data type.
*[Optional] Language*
Type: ../integer/integer-data-type
The new language setting for the report.
## Return Value
*[Optional] CurrentLanguage*
Type: ../integer/integer-data-type
The current language setting for the report.
## Remarks
The Language integer parameter must point to a valid Windows Language Code Identifier (LCID). See Windows Language Code Identifier (LCID) Reference<https://learn.microsoft.com/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f>. The Language codeunit includes the GetLanguageId method that can safely return a valid LCID from a language code in the Language table. If you call Report.Language with an invalid LCID, then a runtime error occurs.
If you have reports that you want to print in the language of the recipient rather than in your own working language, you can add a single line of code in the report to handle this. This functionality is already enabled for most reports in the standard Business Central database. The document is printed in the language that's specified in the Language Code field on the Customer Card page.
For reports that need the multiple document languages functionality, you must insert the following AL code as the first line in the `OnAfterGetRecord()` trigger on the data item referencing the Customer table (notice that the feature isn't limited to the Customer table, other data sources provide similar functionality):
`CurrReport.Language := LanguageMgmt.GetLanguageIdOrDefault("Language Code");`
For each of these reports, you must create a new variable, LanguageMgmt, with the data type Codeunit pointing to the Language codeunit. When you have compiled the object, it'll no longer print in the user's working application language if another language has been specified on the Customer Card page.
## Example
The following example illustrates how to use the Language codeunit to set the language defined on the customer card in a report. The example is based on report 10071 "Customer Stmt. (Pre-Printed)" from the base application.
```al
report 10071 "Customer Stmt. (Pre-Printed)"
{
  // report properties

  dataset
  {
    dataitem(Customer; Customer)
    {
      // data item fields and nested dataitems here

      trigger OnAfterGetRecord()
      begin
        CurrReport.Language := LanguageMgt.GetLanguageIdOrDefault("Language Code");
        CurrReport.FormatRegion := LanguageMgt.GetFormatRegionOrDefault("Format Region");

        // maybe more code here
      end;
    }

    // requestpage section

    // rendering section

var
    LanguageMgmt: Codeunit Language;
}

```
## Related information
Windows Language Code Identifier (LCID) Reference<https://learn.microsoft.com/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f>
reportinstance-formatregion-method
../../devenv-report-localization
report-data-type
Get Started with AL<../../devenv-get-started>
Developing Extensions<../../devenv-dev-overview>

Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/report/reportinstance-language-method, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact. https://jonas-paprotka.de/docs/dev-itpro/developer/methods-auto/report/reportinstance-language-method/
