Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have a ticket open with MS on this but am interested to see if anyone is noticing an issue where their reports in the Service from published PBIX desktop files are not right. Here is what I've found:
As I said, I have a ticket open and have started the initial conversations, but wanted to see if anyone here was experiencing the same issue recently.
On the June 2018 PBID and June 2018 Gateway. These are SQL Server tables. I've not seen this issue on other data types, but most of our data is SQL Server.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingSolved! Go to Solution.
Hi Ed. As I said over email, we've identified the root cause of this issue. We're currently targeting the fix for our July release.
In the meantime, you can work around the issue by ensuring that your folded queries are always sorted. This can be done by always including (and preserving in downstream queries) all primary keys for a given table. Or, if this isn't possible (as in your case when doing a Group By operation), you can explicitly sort by a set of unique keys before combining. (Also note that it may be necessary to buffer after sorting and before combining to ensure the sort is applied by the folding layer. You'll have to experiment to see whether or not this is necessary.)
Ehren
@edhans, This issue should be now be fixed. Please download the Power BI Desktop July release and let us know if things are now working as expected.
Ehren
@Ehren wrote:@edhans, This issue should be now be fixed. Please download the Power BI Desktop July release and let us know if things are now working as expected.
Ehren
Thanks! Already have. So republish and I'm done? No new Gateway needed as well?
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingAh, yes. You'll need the new gateway as well (once it comes out).
Ehren
Thanks. I'll wait until that happens before I make changes to my process. Hopefully soon. Usually the gateway is out by last week of month. Of course, normally desktop is out first or second week of month, and that was later than normal this time.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingYes, this month is a little abnormal. 🙂 I just checked and was told the July gateway should be out soon (in the next day or so).
Ehren
@Ehren I am not sure if this is the same issue or not.
You may recall in my tests I had a PBIX file loaded into my personal workspace that tested three scenarios:
When the new gateway was released last week, I installed it, then for grins republished this report to my workspace and let it go, expecting to never hear from it. It was set to alert me if any of the 3 values above wasn't the same.
Today it alerted me. The Table.Buffer() version is way way way off. Instead of a total of 10,570 rows that #1 and #2 have above, it only has 1,402 rows. Instead of the last 12 months, it only has August 2017, Sept 2017, and August 2018. It dropped Oct 2017-July 2018. That data was pulled from the same source table as Aug-Sep 2017.
The Aug 2018 data is in a separate table in our server and that is what gets appended.
This report has run several times a day for the last week with no issues, and today, it blew up. Let me know if you want the PBIX file or something. I downloaded it from the service when I got the alert. It has already refreshed automatically again and all 3 are in sync.
Or maybe the rollout isn't finalized? I just saw PB145321 in the Office 365 Admin portal.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi @edhans. Yes, it looks like you're hitting the issue described in the admin portal (which was an unintended side effect of the fix for the original issue you were hitting). Do you happen to know which region your PBI service is in? If so, I can let you know when the fix is deployed to your region.
Ehren
I think Western, and I only know that as that is what shows up when I have a sync error, and not 100% sure on that. I am in California if that matters. I don't see where in the PBI admin portal to check that out.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingYou should be able to determine the region by clicking the help question mark in the upper righthand corner of the Power BI website and selecting About Power BI. Look for the line that says "Your data is stored in...".
Ehren
@Ehren wrote:You should be able to determine the region by clicking the help question mark in the upper righthand corner of the Power BI website and selecting About Power BI. Look for the line that says "Your data is stored in...".
Ehren
West US (California) is what it says.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting@Ehren - I am sure your team is working on this, but the Admin portal is either wrong, or there is still a bug you aren't aware of. My test queries using Table.Combine() and Table.Combine() followed by Table.Buffer() still fail on occasion, easily over 25% of the time.
The admin portal says this:
Title: Incomplete or missing data User Impact: Users may see missing or incomplete data when refreshing reports, viewing reports or dashboards. More info: Customers utilizing specific connectors when refreshing datasets without using native SQL queries, pulling SQL data that does not include a SQL primary key column in the final result, and doing Append or Merge operations may experience this issue. The following is a list of connectors impacted: SQL Server, Oracle, PostgreSQL, MySQL, Teradata, Sybase, Informix, DB2 or Access. Current status: The fix deployment has completed restoring functionality for most users. For all remaining premium users still experiencing impact, we anticipate the fix to reach your environment within 24 hours.
I am not premium. We are just standard pro-licenses. I just did a manual refresh at 6am Pacific Sunday morning, and it failed. As indicated earlier, our data is stored in the West US environment. California.
According to the text of the alert, our envornment should not be experiencing this, but we are.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingHi @edhans. This issue has now been fixed in the Power BI service, but the gateway update will be coming in the next day or two. I will email you a private link so you can download the new gateway before it's officially released.
Ehren
@Ehren wrote:Hi @edhans. This issue has now been fixed in the Power BI service, but the gateway update will be coming in the next day or two. I will email you a private link so you can download the new gateway before it's officially released.
Ehren
I think there may be an issue with the November gateway or service @Ehren
I have kept my report running that does the same sales table 3 ways:
Last night, #2 reported different results. Thousands of dollars. The report that is running has not been updated with the desktop in months, but I did just install the Nov gateway yesterday morning.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting
@Ehren wrote:Hi @edhans. This issue has now been fixed in the Power BI service, but the gateway update will be coming in the next day or two. I will email you a private link so you can download the new gateway before it's officially released.
Ehren
Thank you! Trying to restore confidence in the reporting tool hasn't been easy lately. Looking forward to the link.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingSent. Please let me know if it came through.
Ehren
@Ehren wrote:Sent. Please let me know if it came through.
Ehren
Yes. Downloaded and installed. Testing now. Appreciate it.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingI kinda figured this issue was part of the "abnormality"
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingWe're experiencing similar behaviour with our SAP HANA report.
Sometimes the values displayed in our financial reports double but a manual refresh of the data seems to fix it. It's random and a pain to monitor and/or duplicate...
Hi @Aron_Moore. SAP HANA uses a different backend pipeline than SQL, so yours is likely a different issue (although it's possible the root cause is similar). Can you create a new Power BI Community thread for it?
Thanks,
Ehren
I had a thread but hadn't received any input yet. Thought I'd tag along with this one for some ideas/help.
https://community.powerbi.com/t5/Service/Data-duplication/m-p/451485#M47670
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.