Back to Blog

Multi-Language Page Navigation in Power BI - Working Around Untranslatable Page Tabs

November 22, 2026•7 min read•Michael Ridland

If you build Power BI reports for an Australian organisation with operations in Asia, Europe or the Pacific, sooner or later someone asks for the report in another language. We've had requests for Japanese, Simplified Chinese, Bahasa Indonesia and French in the past year alone, usually from mining, education and agriculture clients with regional teams.

Power BI has decent support for translations these days. You can translate table names, column names and measure names in the semantic model. You can translate data values with a bit of extra modelling. You can translate visual titles and labels using measures. But there's one bit that catches nearly everyone out: page names.

Page tabs at the bottom of a report show the page display name, and Power BI has no built-in way to translate it. A Japanese user opens your carefully translated report and the navigation still says "Sales Overview", "Regional Breakdown" and "Customer Detail" in English. It looks half finished.

Microsoft's guidance article, Multiple-language page navigation, describes the workaround. This post walks through it with some notes from projects where we've used it.

The approach in short

The idea is simple once you see it:

  1. Hide every page in the report except one landing page.
  2. Build your own navigation using buttons on each page.
  3. Make the button labels come from measures that return the right text for the user's language.
  4. Use page navigation actions on the buttons to move between the hidden pages.

Hidden pages still work as navigation targets. Users can't see them in the tab list, but buttons can take them there. So the page tabs effectively disappear from the user's experience, and your translated buttons become the menu.

Step by step

Hide the pages

In Power BI Desktop, right-click each page tab and choose Hide page. Leave just one page visible, typically a landing or home page. When the report is published, users only see that one tab, and everything else is reached through buttons.

Some teams go further and hide the page pane entirely in the Power BI service report settings. Either way works. The key point is that nobody should be relying on the tabs to move around.

Create a translation measure for each label

You need a measure per button label that returns the translated text. The standard pattern uses the USERCULTURE() DAX function, which returns the culture code of the user viewing the report, like en-AU, ja-JP or fr-FR.

A simple version looks like this:

Nav Sales Label =
VAR Lang = LEFT ( USERCULTURE (), 2 )
RETURN
    SWITCH (
        Lang,
        "ja", "売上概要",
        "fr", "Aperçu des ventes",
        "id", "Ringkasan Penjualan",
        "Sales Overview"
    )

I prefer matching on the first two letters rather than the full culture code. Otherwise en-AU, en-GB and en-US each need their own branch, and you end up with someone in New Zealand getting the default because en-NZ wasn't in the list.

For anything beyond a handful of labels, hard-coding translations into measures gets painful fast. A better pattern is a translations table in the model with a key column, a language column and a text column, and a single measure that looks up the right value. Then your translators work in a spreadsheet, and you don't need to touch DAX when someone fixes a typo in the French. We've written about translation workflows before if you want more on managing that side.

Build the buttons

Add a blank button for each page. In the button's format pane, turn on the text option and use conditional formatting (the fx button next to the text field) to set the text from your label measure.

Then set the button's Action to Page navigation and choose the destination page. You can also make the destination itself conditional using a measure that returns a page name, which is handy if you want a single dynamic "next" button, but for a standard menu, fixed destinations per button are simpler and easier to maintain.

Group the buttons into a navigation bar, style them consistently, and copy the group onto every page. Power BI's built-in page navigator visual exists, but it shows page display names, which is the exact problem we're trying to avoid. So you build the menu manually.

Highlight the current page

Users like knowing where they are. Since you're building navigation by hand, you also need to handle the "selected" state. The easiest way is to format the button for the current page differently on each page: on the Sales page, the Sales button has a darker fill. It's manual, but with five or six pages it's a ten-minute job.

What works well

Once it's set up, this approach is reliable. The user's language comes from their browser or Power BI service language setting, the measures pick it up, and the navigation just works. We built this for an agriculture client with operations managers in Australia and Indonesia, and the Indonesian team's feedback was that it was the first internal report that felt like it was built for them, not translated as an afterthought.

It also gives you more design control than the default tabs. Tabs are functional but plain. A custom navigation bar can sit at the top or down the left side, use icons, and match your organisation's brand. Plenty of our clients build custom navigation even for single-language reports for exactly this reason. Multi-language support is a bonus on top.

What's still rough

It's a lot of manual work. Every page needs the navigation group. Every new page means a new button, a new measure (or translation row), and updating the group on every other page. Report templates help. Copying the navigation group from a master page helps. But it's still more maintenance than tabs.

Testing is awkward. To see the report in another language, you either change your browser language, change the Power BI service language setting, or add a language parameter to the report URL (for example ?language=ja). The URL parameter is the quickest option for testing. In Desktop, you can't easily preview other cultures without changing your Windows settings, so most of the testing happens after publishing.

Page names still leak in places. The browser tab title, bookmarks, some export options and the Power BI service breadcrumbs can still show the original page name. For most users this doesn't matter, but if you have a strict requirement that nothing appears in English, test the whole journey, including exports to PDF and PowerPoint.

Right-to-left languages. If you need Arabic or Hebrew, translated button text works, but Power BI doesn't mirror the report layout. The navigation will still read left to right. That's usually acceptable, but set expectations early.

Mobile layout. If you've built a mobile layout for the report, the buttons need to go there too. Easy to forget.

Is it worth it?

For a report used by a few hundred people across different language groups, yes. The setup cost is maybe a day of extra work on top of the rest of the translation effort, and the result is a report that feels properly localised.

For a report with three non-English users who all read English fine at work, probably not. Translation of any kind adds ongoing maintenance, and page navigation is the most manual piece of it. Talk to the actual users before committing.

If you do go ahead, my advice is to decide on multi-language support at the start of the project, not after the report is built. Retrofitting custom navigation into a twelve-page report with existing bookmarks and drillthroughs is fiddly. Designing it in from day one is much easier. Our earlier post on locale values in multi-language reports covers some of the model-side decisions that go with this.

We help organisations design and build Power BI reports for multi-region teams through our Power BI consulting practice, and as part of wider Microsoft Fabric data platform work. If you're planning a rollout across language groups, have a chat with us before the first page gets built.