Accelerators & toolsOneStream accelerator · multi-language finance teams2026

Language Translator: one set of OneStream dashboards, every user in their own language

Existing OneStream dashboards are shown to each user in their own language, with no per-language copies to maintain. Each label is translated once, saved, and reused, so cost stays small and finance keeps control of the wording.

Result

Every user sees the same dashboards in their own language

Before: English onlyAfter: each user's languageChange: 1 build

Quick facts

Industry
OneStream accelerator for finance teams that work in more than one language
Role
Designer and developer
Timeline
Built and demonstrated in 2026
Team
Solo build, shaped by how a client demo needed to run
Status
Working accelerator, demonstrated live on a Capital Planning workspace in French and German
Impact
One set of dashboards serves every regional team in its own language (English, French, German and Japanese shown), with no duplicate dashboards to keep in sync, every translation reviewable and overridable, and the whole feature reversible with one click.
  • OneStream
  • VB.NET
  • Google Cloud Translation
  • Dashboards
  • Cube Views
On this page

Overview

Regional finance teams often share one OneStream application, but the labels, buttons, report titles and drop-down lists are all in English. The usual answers are to rebuild every dashboard once per language or to live with English.

Language Translator takes a third route. Dashboards stay in English at design time, and each user sees them translated at run time, in the language set on their own OneStream user profile. It ships as a OneStream workspace with an assembly, so there is no client-side install and no change to how the existing dashboards are designed.

The Problem

  • English-only screens for global users. People who plan and review in French, German or Japanese were working in a second language every day.
  • Per-language copies multiply the work. A copy of every dashboard, cube view and parameter for each language means every later change has to be made again and again, and the copies drift apart.
  • Translation tools are a worry for finance. Teams want to know what was changed, who can correct it, and how to get back to the original if it goes wrong.

How It Works

Four steps take a workspace from English-only to multilingual.

1. Admin Enables

An administrator picks a workspace and a maintenance unit and clicks Enable. That is the only setup per workspace. An admin page also sets each user's preferred language and can pre-translate dimension member descriptions into a chosen language.

2. Text Is Tagged

On Enable, the visible text is tagged for translation: labels, captions, buttons and lists. The dashboards themselves are not redesigned.

3. User Opens the Dashboard

When someone opens a dashboard, their preferred language is read from their OneStream user profile. Nobody has to pick a language each time.

4. Translation Served

Each piece of text goes through a three-step lookup:

  • Quick memory first. Recent labels are held on the server and come back instantly.
  • Saved translations next. Every translation ever made is stored in the OneStream application.
  • Google Translate last, for new text only. The result is saved straight away, so each label is translated once and then reused by every user.

What Gets Translated

  • Components: labels, buttons, tooltips and combo boxes.
  • Cube views: page captions, report headers and footers, and member descriptions.
  • Parameters: drop-down and member lists show translated descriptions.
  • Data adapters: text values in grids, BI Viewers and pivots.
  • Dimension members: descriptions per language, stored in OneStream.
  • Admin overrides: correct any translation and the change applies immediately.

Text that should never change is skipped automatically and reported: formulas, parameter references, numbers and existing business-rule expressions.

Built for Control and Audit

  • Review and override. Admins can edit any translation. Overrides take effect immediately and are reused from then on.
  • Full audit trail. Every Enable or Disable run writes a status file listing the original text, the new text and the outcome, including what was skipped.
  • Reversible. Disable restores the original English text.
  • Removable. Uninstalling removes the workspaces, stored translations and dashboard profile it added.

What It Costs

Only new text is ever sent to the translation service, so cost is small and mostly one-time. Using Google Cloud Translation list pricing as of October 2026:

  • The first 500,000 characters each month are free.
  • After that, the rate is $20 per million characters.
  • A typical rollout of 10,000 members at about 30 characters each, in 3 languages, is about 900,000 characters, roughly $8 once.

More users, reopened dashboards and refreshes add no cost, because they are served from saved translations.

Results

MetricBeforeAfterChange
Dashboard languageEnglish onlyEach user's own language1 build
Dashboard copies per languageOne full set per language, kept in sync by handNoneno duplicates
Translation of a repeated labelNot applicableTranslated once, reused by all usersone-time
Wording correctionsEdit each copyOne override, applied immediatelyinstant
Rollout cost (typical example)Not applicableAbout $8 one-time at list pricelow

Soft outcomes:

  • Finance owns the wording. Key terms can be reviewed and corrected by the people who use them.
  • Safe to try. A pilot on one workspace can be switched off and the screens go back to English.
  • Fast after the first view. Quick memory and saved translations mean the translation service is not called again for text it has already seen.

Learnings

What worked. Translating each label once and storing it. That one design choice keeps screens fast, keeps cost predictable and gives finance a single place to correct wording.

What I'd do differently. Review the core finance terminology with the business owners before the first rollout. Machine translation is good at general text, and the terms that matter most to finance are the ones worth agreeing up front.

Skill developed. Designing a feature so it can be undone. The status file, the Disable step and the clean uninstall are what make a business comfortable turning it on.

Need something like this built?