Forum Discussion
Missing rows in table view
Just to double check, have you refreshed the data preview in the Query Editor recently? Just wanting to check that the data you're looking for is still in the data source itself.
If it's there, but not showing up in Table view, be sure to right click the top of the column and clear all filters. I know that I've definitely gone crazy trying to find a specific entry, but was unable to find it because I had forgotten an old filter from a few hours ago.
If it STILL doesn't show up, try filtering in ONLY the missing data from the Query Editor and see if it shows up in your visuals. It would also be helpful if you could recreate a subsection of the data and share the .pbix with us.
- Theo14036 years agoAdvocate I
Hello tarunsingla Cmcmahan
I refreshed data and checked that no filters are active in table view. In my query I added a filter to just filter the missing records. In query editor the missing rows are visible, but they are not visible in table view and therefore also missing in my report. Seems like a bug in Power BI to me. See screenshot which shows the same table in query editor and in table view. Table in table view is empty.
Regards Theo
- MarkPalmberg1 year agoKudo Commander
You're right, Theo1403 , this is definitely a bug. Version: 2.137.751.0 64-bit (October 2024)
- Cmcmahan6 years agoResident Rockstar
At the top of the Query Editor, you've got a bar that tells you that the data preview is 108 days old, and may be out of sync.
Hit the refresh button, and it should fix your discrepancy.
- MarkPalmberg1 year agoKudo Commander
Follow up here upon the resolution of my service ticket with MSFT. tl;dr: It was a case sensitivity issue with my merge keys.
tl: I have 2 SQL server data sources in my PBIX. In Query A (azure SQL server), my merge key is uppercase. I add a transform step there to lowercase that column.
In Query B (on-prem SQL server), my merge key *appears to be* lowercase straight from the SQL server when viewed in Power Query. And in fact, when I merge the two queries without any transformation of my merge key in Query B (because why would I? It looks like it's lowercase!), the merge appears to be successful; I can see merged columns in the Power Query view.
When I Close & Apply and add all columns from my merged dataset to a table visual, *no* column values from Query B appear in the table.
When I go back and add a lowercase transform step to Query B prior to the merge step, everything then works. The MSFT support team sent along this nice Chris Webb post on the subject as a means of explaining what I'm seeing, which is fine, but I'm not sure an end user should ever see accurate merged results in the Power Query and then *not* see them in a table view. That's just not great UX, case (in)sensitivity be damned.