This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowJuly 28 - August 9 | Final Round of the Power BI Dataviz World Championships. This is your chance. Learn more
Hi all, we're in the process of moving a supply chain dataset away from being an old-style "import" dataset and instead using a Fabric warehouse to store the data. I'm trying to reconcile a number of missing purchase orders between the two systems. I thought I'd be able to:
1. Create a validation lakehouse
2. Shortcut to the PO table in the lakehouse
3. Shortcut to the PO table in the semantic model using OneLake integration (https://learn.microsoft.com/en-us/power-bi/enterprise/onelake-integration-overview)
4. Write a simple SQL statement to compare the PO IDs between the two systems
However, hitting issues with this. In step 3 - I am able to shortcut to the table in the semantic model into my validation lakehouse, once all the requirements were met. When I switch into the SQL view of the validation lakehouse however that table does not show up. I'm a bit unsure - it's great to add the table to the lakehouse, but if you can't then actually use it with SQL, what's the point?
Have I done something wrong - should the table be showing up in the SQL endpoint view?
Thanks,
Scott
Solved! Go to Solution.
Hi @Scott_Powell ,
According to this document: Learn about Microsoft OneLake Delta table integration in Power BI and Microsoft Fabric - Power BI | ...
This feature is currently in preview. During preview, shortcut tables built on top of the exported model in Lakehouse can't be queried by using the SQL endpoint.
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Scott_Powell ,
According to this document: Learn about Microsoft OneLake Delta table integration in Power BI and Microsoft Fabric - Power BI | ...
This feature is currently in preview. During preview, shortcut tables built on top of the exported model in Lakehouse can't be queried by using the SQL endpoint.
Best Regards,
Xianda Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
If you love stickers, then you will definitely want to check out our community sticker challenge, Barcelona edition!
Check out the July 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 5 | |
| 5 |