Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
What is going on? Surely their Google Chrome setup to change language shouldnt affect data output? I checked and double checked, they do not have any filters to remove the Open
Solved! Go to Solution.
Get your user to try clicking this button in the top right.
It looks like they've used the filter pane or something to apply a filter to only show closed items.
Hi @mikemetrics , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
Thank you.
Get your user to try clicking this button in the top right.
It looks like they've used the filter pane or something to apply a filter to only show closed items.
Hi @mikemetrics , Thank you for reaching out to the Microsoft Community Forum.
I think the root cause is a combination of Row-Level Security (RLS) filtering out data, locale settings affecting date formats, and potential data refresh inconsistencies. To fix this, let’s try below:
Go to Power BI Service -> Workspace -> Dataset -> Security. Check if any roles are applied that might be filtering Status = "closed", which would prevent "Open Issues" from showing. If RLS is active, modify the rule to include all statuses. If RLS isn’t needed, remove the role entirely. To confirm the fix, use the "View as Role" feature to simulate what your consumers see. Once this is done, all 15 issues should be shown.
Your consumers browser locale is set to Spanish, which is causing MM/DD/YYYY dates to be displayed as DD/MM/YYYY. Power BI automatically formats dates based on the user’s browser settings unless explicitly defined. To ensure consistency, go to Power BI Desktop, select all relevant date columns, navigate to the Modeling tab, and set the Format to "MM/DD/YYYY". Additionally, for displayed dates, create a calculated column. This ensures all users see the same date format, regardless of their locale.
Go to Power BI Service -> Workspace -> Dataset -> Refresh History and check when the last successful refresh occurred. Perform a manual refresh, then ask consumers to clear their browser cache (Ctrl + F5) and reload the report. This guarantees they are viewing the latest dataset with all 15 issues. If necessary, adjust by adding or subtracting hours based on your region. Also, since reports will be used globally, test them with different browser locales (Spanish, French, English) to ensure consistent behaviour.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @v-hashadapu
That is actually helpful as I didnt know about RLS for future use. But the model doesnt actually have any rules setup. I suppose this is not the culprit, see snip.
Also, some new bit of info: I have Issues on a dedicated tab, plus a dashboard with other metrics.
My consumer in Spain still cannot see Open Issues on the dedicated tab, but they can see them on the Dashboard. Fascinating....
I have just rechecked my model, I have no filters from one tab to the next - > but it shouldnt be an issue anyway because on my online view of the report I can see Open issues on both tabs.
Help please
Hi @mikemetrics , Thank you for reaching out to the Microsoft Community Forum.
First, ask your consumer to click the "Reset to default" button (top-right, near Copilot) in Power BI Service to clear any filter on the dedicated tab. This should restore all 15 issues, matching the dashboard. Next, fix the date format by setting each date column’s "Format" to "MM/DD/YYYY" in Power BI Desktop’s "Modeling" tab. Use this DAX:
FormattedDate = FORMAT([DateColumn], "MM/DD/YYYY")
in visuals for consistency across locales.
Then, ensure data alignment by checking the dataset’s "Refresh history" in Power BI Service, forcing a manual refresh, and asking your consumer to clear their browser cache (Ctrl + F5). Finally, for global use, replace TODAY() with:
AdjustedToday = UTCNOW()
and adjust for timezone if needed. Test with different locales to confirm consistency.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Surely their Google Chrome setup to change language shouldnt affect data output?
That's exactly what should happen - that is how the culture handling is designed. You would need to materialize strings to prevent this from happening.
Not sure if this is Report Server or Power BI Service - keep in mind that Power BI Service runs on UTC, and your user's "Today" may not be your "Today" and may not be the service's "Today".
Hi @lbendlin
Replying to each of your comments
"That's exactly what should happen - that is how the culture handling is designed. You would need to materialize strings to prevent this from happening."
Appreciate this might change the date setup. Why is it filtering part of the data? What setup would be filtering part of the data once a PBI user issues a report? This is big for me as there will be worldwide reports to issue.
"Not sure if this is Report Server or Power BI Service - keep in mind that Power BI Service runs on UTC, and your user's "Today" may not be your "Today" and may not be the service's "Today"."
Yes noted on UTC agreed. Tried to refresh the report later in the day and it still appears that there are part of the data "filtered out".
The issue here is not time/region. The issue here is that an entire set of data is filtered out without any filter applied from PBI user to consumer (in another country)
User | Count |
---|---|
6 | |
4 | |
2 | |
2 | |
2 |
User | Count |
---|---|
6 | |
3 | |
3 | |
2 | |
2 |