User Profile
GregMarbais
Kudo Collector
Joined 6 years ago
User Widgets
Contributions
Re: Error fetching data for this visual - Report with Direct Query to Lakehouse
v-saisrao-msft I tried the direct lake capability but had the same issue so I'm going to mark my post summarizing what Tech Support and the Product Group said as the solution - hopefully that will resolve it long-term.1.3KViews0likes0CommentsRe: Error fetching data for this visual - Report with Direct Query to Lakehouse
Hey v-saisrao-msft, The product team doesn't consider it a bug but that this is how the SQL endpoint is supposed to work. So they consider the change they're working on as an improvement. It's not yet released to private preview but it is being worked on (so I'm told - I actually don't have proof). The issue is that the SQL endpoint doesn't automatically refresh after some period of not being active. So for lakehouses that are accessed relatively infrequently - like daily - they need to be manually refreshed using the Refresh Metadata button on the SQL Endpoint for the lakehouse. Then it will automatically refresh for a little while but if it's not accessed again until (say) the next day, it'll shut off again. My problem is the users access the report daily but don't have access to the lakehouse. They're not tech savvy enough. So I'm looking at the direct lake option or eliminating that lakehouse and pointing back to one that is accessed more frequently even if the data acess gets messy. Neither are great solutions.1.4KViews0likes2CommentsRe: Error fetching data for this visual - Report with Direct Query to Lakehouse
v-saisrao-msft The issue hasn't been resolved but I've been told by the Tech Support team that the product team is working on a long-term fix. The issue has to do with how frequent the SQL endpoint refreshes metadata in lakehouses that aren't used often. I have to change things around in the lakehouse and report before I can use direct lake so I'm going to try that but I'm not going to get a chance to do that for a bit.1.5KViews0likes4CommentsRe: Error fetching data for this visual - Report with Direct Query to Lakehouse
lbendlin, Yep, the direct query is to the SQL endpoint. I haven't played with direct lake at all yet. These reports pre-date the launch of direct lake for reports. I'll give that a shot and maybe it gets around whatever is happening under the hood in these lakehouses.1.7KViews0likes0CommentsRe: Error fetching data for this visual - Report with Direct Query to Lakehouse
v-saisrao-msft I'm not sure what you mean by updating the lakehouse shortcuts - I've definitely recreated them multiple times - at all points along the chain of lakehouses. The ingestion pipelines run regularly so they've definitely re-run many times since this behavior started. I'm pretty sure the issue is local to the workspace and lakehouse - the same tables showing the issue are working fine for other reports in other workspaces, pulling from other lakehouses. I've never done a metadata initialization query so I'll have to look into that. And will look into Direct Lake as an option as well.1.7KViews0likes7CommentsError fetching data for this visual - Report with Direct Query to Lakehouse
Hey all, I'm hoping someone on here may be able to help me. I've already entered a ticket and been in a back and forth with them but getting nowhere 😞. On a daily basis, I have a few reports that I will go into where the visuals are all errored out. The detail of the error message says "Error fetching data for this visual. Failed to complete the command because the underlying location does not exist." Then it has the specific table and a few other details. Here's the crazy part - the table exists in the lakehouse AND when I view the table in the lakehouse (pull it up to see the rows of data), it works fine. EVEN WEIRDER - I can then go back to the report, refresh the visuals and it all works fine!!! This is a workaround that I found even before I put the support ticket in. The crazy part is that the table that is mentioned in the report is my date table and it's refreshed weekly but the error happens daily. On occassion, I do see the error for other tables. The same workaround works. Those tables tend to be refreshed daily or more frequently. What's even more weird - this same exact table is accessed in many other lakehouses and many other workspaces that don't have this issue at all. It's isolated to a few workspaces (less frequently used) and their lakehouses and reports... ALL of the tables that are mentioned in the error messages are used in other workspaces and many other reports which do not exhibit this behavior. More on my structure: The report pulls data from a Lakehouse using direct query. The table is a shortcut to another workspace where I manage the data that comes in. I've built out a medallion architecture and then create a lakehouse for each user group in their own workspace. The lakehouse in the user's workspace links back (via shortcut) to a lakehouse that I use to serve the data - it basically is a bunch of shortcuts back to the most refined version of each table. The date table that is usually the issue is created in a notebook and saved in a lakehouse. The date table shortcut goes back to the lakehouse where the data is actually stored. The other table shorcuts go back to a lakehouse which has a shortcut to the data warehouse where the data is stored. We have an F64 sku. I've built up a bunch of pipelines to process our data and provide it for reporting. I've been using Fabric since it was in preview. For the date table, that means: Shared Tables Lakehouse --|new workspace|-> End User Lakehouse (via Shortcut to the Serving Lakehouse) ---> Semantic Model via direct query For most of my other tables, this means: Staging LH ---> Raw Datawarehouse ---> Clean Datawarehouse ---> Refined Datawarehouse ---> Serving Lakehouse (via shortcut to DW) --|new workspace|-> End User Lakehouse (via Shortcut to the Serving Lakehouse) ---> Semantic Model via direct query What I've tried: Deleted and recreated the shortcut - didn't work Deleted and recreated the lakehouse - didn't work Rebuilt the Semantic model - didn't work Submitted a support ticket to Microsoft They escalated to the PG team after some troubleshooting The PG team told the tech support team that my users and I just have to go into the lakehouse each time, pull up the table, then refresh the data in the report 😳 (Which I reminded them is the workaround I told THEM about and isn't a solution because it really shouldn't work this way and doesn't in other places) I'm trying to avoid completely recreating the Workspace. I'm also trying to avoid copying the data from the source lakehouse to the end user's lakehouses - that would undermine the value of Fabric. Has anyone else seen this and, if you have, found a fix?Solved1.8KViews0likes12CommentsLinked Table display rows of NULL data
Hey Everyone, I'm thinking this will need to be a support ticket but wanted to see if anyone else has seen this. Basically, I have a whole medallion architecture set up which processes data. I link the processed tables to a Lakehouse which I then serve to users. So each user group has their lakehouse that links back to the processed table lakehouse which links back to data warehouses (generally no more than 2 links in the "chain"). Recently, tables that had been working just fine in the user group lakehouses have started being a problem randomly. Basically, one of the linked tables will show a table of nothing but null values. When viewed through the lakehouse, datawarehouse, via PowerBI desktop, dataflows - they all show the linked table is just a bunch of rows of null values in each column. It happens randomly (or at least in no way that I can think of). I'm able to solve it by deleting the linked table and waiting a minute or two then recreating the linked table. So far the easiest thing is to just fix it rather than preserve it and report it to Microsoft. Has anyone else seen this? Anyone know of a permanent solution?Solved1.4KViews0likes5CommentsRe: Incremental Refresh with Deleting Duplicate Records before Appending Staging Data
simarsokhi I know Dataflow Gen2 does support incremental refresh now. Last time I tried (it's been months), Dataflow Gen2 required that the table has a created at timestamp and an updated at timestamp as two separate columns. I believe they were working to improve that experience so you can just use an updated at timestamp but I don't know if Microsoft has launched that feature yet. I also found the Dataflow Gen2 tended to use more capacity to do the incremental refresh.7.3KViews2likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.