Forum Discussion
Lumel PowerTable
Hi Rajaniraor,
Hope you're doing well!
Question 1: Can PowerTable consume data from multiple sources directly within the same table?
No, not natively within a single PowerTable instance. PowerTable is designed to connect to one data source per table app. Its core architecture pushes down all SQL processing directly to the connected database sink, with no data replication on its side. (Lumel) This means each table is tightly bound to a single connection.
There is also a specific and important limitation regarding the Lakehouse: PowerTable can read from Lakehouse SQL endpoints but cannot write back to them, because the Lakehouse's SQL endpoint is read-only by design, this is an inherent constraint of the Delta Lake open-source protocol, not a Microsoft design flaw. (Lumel)
Question 2: What is the recommended approach to combine data from multiple sources?
The recommended approach is to consolidate your data upstream, before it reaches PowerTable. Concretely, you have two solid options:
Option A: Use a Fabric Data Warehouse as your unified layer: In Fabric, the Lakehouse SQL analytics endpoint uses the same engine as the Warehouse, which means you can combine both sources in your Warehouse using cross-source views or queries. (Microsoft Learn) You surface the Lakehouse attributes you need into your Warehouse (via shortcuts or views), and PowerTable connects to a single, unified Warehouse table or view.
Option B : Use a Fabric Shortcut or Dataflow to bring Lakehouse data into the Warehouse: Move or reference the required Lakehouse attributes into your Fabric SQL Warehouse, so PowerTable has everything it needs from one endpoint. The recommended workaround pattern is to implement writeback in SQL Database or Warehouse as a transactional store layer, keeping it separate from the Lakehouse. (Lumel)
Hope this helps! Don't forget to mark as solution and thumbs up in order to keep helping others.
Oussama (Data Consultant - Expert Fabric & Power BI)
3 Replies
- v-echaithra
Community Support
Hi Rajaniraor ,
Thank you oussamahaimoud for your inputs.
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you. - oussamahaimoud
Memorable Member
Hi Rajaniraor,
Hope you're doing well!
Question 1: Can PowerTable consume data from multiple sources directly within the same table?
No, not natively within a single PowerTable instance. PowerTable is designed to connect to one data source per table app. Its core architecture pushes down all SQL processing directly to the connected database sink, with no data replication on its side. (Lumel) This means each table is tightly bound to a single connection.
There is also a specific and important limitation regarding the Lakehouse: PowerTable can read from Lakehouse SQL endpoints but cannot write back to them, because the Lakehouse's SQL endpoint is read-only by design, this is an inherent constraint of the Delta Lake open-source protocol, not a Microsoft design flaw. (Lumel)
Question 2: What is the recommended approach to combine data from multiple sources?
The recommended approach is to consolidate your data upstream, before it reaches PowerTable. Concretely, you have two solid options:
Option A: Use a Fabric Data Warehouse as your unified layer: In Fabric, the Lakehouse SQL analytics endpoint uses the same engine as the Warehouse, which means you can combine both sources in your Warehouse using cross-source views or queries. (Microsoft Learn) You surface the Lakehouse attributes you need into your Warehouse (via shortcuts or views), and PowerTable connects to a single, unified Warehouse table or view.
Option B : Use a Fabric Shortcut or Dataflow to bring Lakehouse data into the Warehouse: Move or reference the required Lakehouse attributes into your Fabric SQL Warehouse, so PowerTable has everything it needs from one endpoint. The recommended workaround pattern is to implement writeback in SQL Database or Warehouse as a transactional store layer, keeping it separate from the Lakehouse. (Lumel)
Hope this helps! Don't forget to mark as solution and thumbs up in order to keep helping others.
Oussama (Data Consultant - Expert Fabric & Power BI)
- v-echaithra
Community Support
Hi Rajaniraor ,
We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.