Forum Discussion
fabric data warehouse
Helo,
In microsoft fabric I have created ADF pipelines to ingest data into data warehouse.
I also created lakehouse with shortcuts to data warehouse tables.
Question
from power bi desktop, I go to Get data, Fabric and select lakehouse (lh) or warehouse (wh).
Power bi does not show the tables in lh/wh. Anything I should do?
Thanks
22 Replies
- AnonymousNot applicable
please note that power bi is only able to see the tables if I create a semantic model.
But I want to see why power bi does not see the tables in lh or wh
thank you
- AnonymousNot applicable
Hi Anonymous
If you want to define your own data model you need to connect to the SQL endpoint.
https://learn.microsoft.com/en-us/fabric/data-warehouse/create-reports
I created a new warehouse.
When you click on connect the existing tables in the semantic model of the Fabric Warehouse will be displayed in Power BI.
When you click on Connect to SQL endpoint, you can create your own model.
You can select the tables when connected to SQL endpoint:
You can choose Import or Direct query as per your requirement.
When you click on load,the desired tables will be seen in Power BI desktop.Hope this helps. Please let me know if you have any further questions.
- AnonymousNot applicable
Hi Anonymous
We haven’t heard from you on the last response and was just checking back to see if your query got resolved. Otherwise, will respond back with the more details and we will try to help.
Thanks
- AnonymousNot applicable
Hi Anonymous
Thanks for using Fabric Community.
Are you following the below steps:
After making the connection, you can find the tables. Please let me know if the issue still persists.
Hope this helps.- AnonymousNot applicable
yes, I am following the steps but power bi does not show the tables
- kasun_rumesh
Helper II
Did you find any solution for this? I'm also facing the same issue
- shashankgFrequent Visitor
Dear Microsoft Team,
I am encountering the same issue that user ‘arkiboys’ reported. I sincerely hope that this issue receives prompt attention and resolution. To address this matter, I have raised a Service Request (SR) with the reference number 2407010050000090 through Microsoft support.
- frithjof_v
Community Champion
What happens if you try the following:
1. In your Fabric workspace, click on the ... symbol next to your Warehouse.
2. Select 'Copy SQL connection string'.
3. Click Copy
4. Create a new report (Blank report) in Power BI Desktop.
5. In Power BI Desktop, click SQL Server
6. Paste the SQL Connection String and click OK
7. Are you able to select the warehouse from the Navigator?
If not, sounds like there is an issue/bug or lack of permission.
Another thing you could try:
1. Create a new report (Blank report) in Power BI Desktop
2. Create a Blank Query
3. Click Advanced Editor
4. Remove all code contents and paste the following code (insert your specific details):
let Source = Sql.Databases("//INSERT YOUR SQL CONNECTION STRING HERE//"), Warehouse = Source{[Name="//INSERT YOUR WAREHOUSE NAME HERE//"]}[Data], Table = Warehouse{[Schema="dbo",Item="//INSERT YOUR TABLE NAME HERE//"]}[Data] in Table5. Then click Done.
This should connect to your table in the Fabric Data Warehouse if you have access.
To check if permission / using wrong user is the issue, then you could select Data source settings:
Select the connection to your Fabric Workspace / Data Warehouse.
Click "Clear Permissions".Confirm by clicking "Delete".
Click "Refresh Preview":
Click "Edit credentials":
Select "Microsoft account" and "Sign in":
Then sign in with the same user account which has access to the data warehouse in the Fabric workspace.
Afterwards, click "Connect".
If that doesn't work, and you know that the user has the necessary permission level to the Fabric workspace / data warehouse, then it sounds like an issue/bug.
- shashankgFrequent Visitor
I got an error after step 5 as mentioned above
- frithjof_v
Community Champion
Interesting.
What happens if you click Edit?
Does this happen also for warehouses in other workspaces?
Did you try the steps I mentioned under "Another thing you could try:". Including the part about clear permission and then sign in again with Microsoft account.