> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/formula-syntax/measure-column-selection-functions/getlocalelabel.md). # GETLOCALELABEL You can configure translations in Inforiver based on the language settings in Power BI. If your report has a global audience, you can configure calculated rows/columns or column groups to display dimension categories based on pre-defined translations when the language is switched. ## Syntax ```javascript GETLOCALELABEL('Label') ``` ## Arguments Label – The Key configured in Localization settings. Required. ## Return value Value corresponding to the Key as defined in Localization Settings. ## Example In this example, we'll demonstrate how to convert product names and custom groups with the GETLOCALELABEL function. {% hint style="info" %} * **Writeback Matrix:** Navigate to Settings > Global Settings> Localization Settings to create translation entries. * **Reporting Matrix:** Navigate to Display Settings > General > Localization Settings to create translation entries. * The screenshots shown in this section are from WB Matrix, but the functionality is the same. {% endhint %}

Use the GETLOCALELABEL function in the Title field and pass the Key specified in the translation config.

Use GETLOCALELABEL and pass they key in the Title

Similarly, when you create custom groups, use the GETLOCALELABEL function. [Learn more about creating column groups](https://docs.inforiver.com/formula-syntax/measure-column-selection-functions/pages/YLohLmBggoc1bG4qjYE5#id-1.-group-columns).

Creating custom groups with localization settings

Notice how the row categories and column groups are implicitly changed to French and German.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.inforiver.com/formula-syntax/measure-column-selection-functions/getlocalelabel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.