To test a Power BI date format with readers in two locales, publish a controlled report, open it with two different browser locales, and compare the same date in several visual elements. This helps report authors and reviewers distinguish formatting that follows a reader’s browser from formatting fixed by the report. The guide applies to Power BI Desktop and the Power BI service; interface labels can change over time.
Prerequisites
- Tools: Power BI Desktop or access to a Power BI report in the service, a small date table, and two browser profiles or devices with different language and regional preferences.
- Time: About 20–40 minutes, depending on report publishing and access setup.
- Difficulty: Easy.
Step 1: Choose an unambiguous test date
Use a date whose day is 13 or higher, such as March 14, 2025. A value like 03/04/2025 is a poor test because one reader might interpret it as March 4 and another as April 3. Keep the underlying date value the same for both readers.
Create or use a date column with that date and add it to a table visual. Include a date slicer and, if relevant to your report, a chart with date axis labels. Microsoft documents that some visual elements, including slicers and Cartesian axis tick labels, can use the viewer’s browser locale rather than the model format string.
Step 2: Set up two reader locales
Use two separate browser profiles or devices so each reader has a distinct language preference—for example, English (United States) and English (United Kingdom). In the Power BI service, a user can also choose a service language under Settings > General > Language. For this test, record both the browser language/region and the Power BI service language, because they are separate settings.
For Desktop-only checks, remember that Power BI Desktop’s default number and date formatting comes from Windows Region settings. A Desktop preview alone does not prove how a service reader’s browser will render locale-sensitive elements.
Step 3: Publish or share one controlled report
Use the same report, dataset, filters, and page for both readers. Give them view access and ask them to open the report in Reading view. Avoid changing the report between checks. Note the date shown in the table, slicer, chart axis, and any date field in the Filter pane. This gives you a comparison across visual elements instead of relying on a single label.
Step 4: Record the first reader’s output
Have Reader A record the visible date text and take a screenshot of the report page. Include the browser’s language and region, Power BI service language, date in the table, and date shown in the slicer and axis. Do not infer that a different display string means the stored date changed; this test compares presentation, not the model’s underlying value.
Step 5: Repeat with Reader B
Have Reader B open the same report in their own browser profile and repeat the observations without changing filters or report settings. A date such as March 14, 2025 may appear with a different ordering or separator in locale-aware elements. Compare the screenshots and write down exactly which elements changed. The table or another visual may behave differently from the slicer or axis, so treat each element as its own result.
Step 6: Decide whether to preserve or standardize formatting
If reader-local formatting is useful, document that behavior for the report audience. If locale-aware values should display consistently, set the report’s Default format string locale for dates and numbers. In Power BI Desktop, open File > Options and settings > Options, then under Current file select Regional settings and choose the locale. In the Power BI service, use the report’s Reading view, choose File > Settings, set the locale, save, and refresh the browser. Microsoft says this setting affects how values display in visuals; it does not change the semantic model’s user-culture awareness. For example, USERCULTURE and metadata translations still use the viewer’s browser locale.
Rerun Steps 4 and 5 after changing the report locale. If the requirement is a specific literal layout rather than locale-aware formatting, consider a custom format string for the relevant model field or visual. Power BI supports formatting at model, visual, and visual-element levels; the visual-level format can override the model format. For details, see Microsoft’s guides to setting a report’s default format string locale, custom format strings, and Power BI language and regional settings.
Troubleshooting
- Both readers see the same format: Confirm their browser profiles actually have different language or regional preferences, then reload the report. Check whether the report’s default format string locale is set to a fixed locale.
- The slicer changes but the table does not: That can be expected. Microsoft notes that certain visuals use browser locale for date formatting, while other values can follow their model or report format. Record results per visual rather than expecting one global behavior.
- A custom format has unexpected output: Check which formatting level you edited and the syntax expected there. Power BI documents visual-level custom formats as using .NET tokens; model and element levels use documented VBA-style tokens. Also check for a visual display-unit override when custom formatting appears not to apply.
Frequently asked questions
Does changing the report locale change the actual date?
No. The default format string locale setting changes how values display in visuals. It does not alter the stored date or make the semantic model’s USERCULTURE return the selected report locale.
Can the Power BI service language alone test regional date formatting?
It is not enough to assume so. The service language controls the service experience, while Microsoft documents browser locale as the source for some visual date labels. Record both settings and compare the visuals directly.
Why do date labels differ between a slicer and a chart?
Visual elements may apply formatting differently. Some slicers and Cartesian axis tick labels can use browser locale to save space or show appropriate detail. Test the exact elements your readers use.