Recent Discussions
Export data via summarized data showing blank value in file
Hi Team, while I am exporting data from a pie chart visual in power bi service via summarize data getting blank file there is no data available in that export file. I am using import mode with implicit measure what could be the reason. But the same 2 columns working fine under matrix and table while exporting data via data with current layout but showing blank as well in summarized data.
Needle in a Haystack?
Hi, i inherited an import pi report with an auxiliary like table called Measure_Metrics. That table has over 100 calculations in it like Sales-MTD. When i hover over the table, rather than a refresh date i see "Invalid Date". There are no records in it in the desktop environment. Would finding what causes the "invalid date" error in a table with over 100 calcs be like finding a needle in a haystack? Or is there a way to better pinpoint which calc(s) is/are causing the problem? Our eyes were drawn to the issue when a number of kpis started showing double dashes rather than actual values.
Datasets shows 'Different' in Deployment Pipeline after successful deployment
Hello Community, Need your help in a issue regarding Deplyment Pipeline in Power Bi. We are using deployment pipeline for more than a month and evrything was smooth and working as expected. Since last 2 days, Deployments are successful from DEV to TEST but datasets showing 'Different' though we have deployed dataset from DEV to TEST. Report is not showing anything but this problem is only for Dataset level. We need some ideas on how to best troubleshoot what is causing the dataset to be different, after a successful deployment from DEV to TEST. After issue in first Dataset, the issue is continuing in rest of the others which were deployed after that. For testing, we have deleted the whole report from DEV & TEST workplaces and again published the same report into DEV and tried to deploy it into TEST through the same deplyment pipeline. so now this was the fresh deployment going but the same issue continues. Deployment was successful but Datasets difference is showing. Basically, We've already remove all datasets from DEV and TEST workspaces and try to deloy everything once again, but it still not working. Please note: we have RLS implemented in our power bi reports. Please help me to sort out this issue as this is on Prioty for us. Thank you.
Staging LH & WH expired credentials
Hi, Account A created a DFgen 2, as you know these come with hidden staging LH and WH. Account B took over the dataflow and destination warehouse (gold WH). Account A has since been archived. All worked for almost 60 days, but dataflows are failing. Disabling the staging features in the dataflow allowed account B to run one particular dataflow, however for the other DF that pushes into warehouse, staging cannot be deleted. Reading the mashup error message clearly states that tokens for account A have expired, and also provides the id of staging LH and WH. How can I now take over and own these HIDDEN LH and WH with account B so that the DFsG2 stops failing? Is there a way we could have prevented this - assuming account A would have still created the intiail DFs -. Thanks,
Power BI Embedded: Last User's Database Parameter Affects All Users
Hi, We have a Power BI report embedded in our .NET application. We use DirectQuery, and our SQL Server production environment contains around 1,800 databases. In Power BI, we pass a database parameter to connect the report to the appropriate district's database. We also use an on-premises data gateway. The gateway data source connection is updated dynamically using the Power BI Update Datasource REST API. Based on the server and database values, we update the corresponding database parameter in the Power BI report. Each user belongs to a specific district, and the report should display data only from their respective district/database. We are facing an issue when multiple users log in at the same time. For example, User A logs in from District A, and the report connects to the District A database and displays the correct data. Then User B logs in from District B, and the gateway datasource and database parameter are updated for District B. After User B logs in, User A also starts seeing District B data. It appears that the latest updated gateway datasource/database parameter is being used by all users instead of maintaining a separate database connection for each user's embedded report session. Our current architecture is Power BI Embedded with a .NET application, DirectQuery, an on-premises data gateway, and approximately 1,800 SQL Server databases in production. The gateway datasource is updated through the Power BI Update Datasource REST API based on the server and database required for the user. What is the recommended approach for this architecture? How can we ensure that each user's embedded Power BI report independently connects to the correct database without affecting other concurrent users? Would Dynamic RLS, effective identity, separate datasets/datasources, or another Power BI Embedded approach be appropriate for this scenario? Any guidance on how Power BI handles gateway datasource updates, parameters, and DirectQuery connections for multiple concurrent embedded users would be greatly appreciated. Thanks!
Date.From(datetimezone) returns different results when using On-Premises Gateway
Hi all, I found what appears to be a date conversion inconsistency in Power BI Dataflow Gen1 when an On-Premises Data Gateway is used. Power BI Dataflow Gen1 Power BI Service Same workspace Same dataflow Comparison : Without gateway & With on-premises gateway let UTC = DateTimeZone.UtcNow(), JST = UTC + #duration(0,9,0,0), Date1 = Date.From(JST), Date2 = Date.From(DateTimeZone.RemoveZone(JST)) in #table( {"UTC","JST","Date1","Date2"}, {{UTC,JST,Date1,Date2}} ) Expected Result：Both Date1 and Date2 should return the same date because they represent the same instant. Date1 = 2026-08-31 Date2 = 2026-08-31 Actual Result： Without gateway: Date1 = 2026-08-31 Date2 = 2026-08-31 With gateway: Date1 = 2026-09-01 Date2 = 2026-08-31
