topic Re: Connecting a Power App to a Fabric warehouse repository in Data Warehouse

Connecting a Power App to a Fabric warehouse repository

pmscorca — Sun, 02 Feb 2025 22:01:41 GMT

Hi,

I need to design a solution to migrate a SQL Server database to a Fabric warehouse with the goal to maintain the existing stored procedures. In this scenario, the Fabric warehouse represents the data repository and the front-end component should be represented by a Power App. In other terms, a Power App should allow to read from and write to a Fabric warehouse directly without any intermediate data passages: so, if it occurs to use Dataverse mandatorily, it is important that the data are saved in the warehouse and Dataverse should limit itself to create simply a link/shortcut against the Fabric warehouse data.

Now, is it possible to implement a such scenario in these terms (no data have to reside into Dataverse)? Thanks

Re: Connecting a Power App to a Fabric warehouse repository

lbendlin — Mon, 03 Feb 2025 02:15:30 GMT

A Fabric Datawarehouse has a SQL endpoint. Until recently that was read-only but i think that limitation has now been lifted. In addition Fabric now offers its own SQL databases.

SQL database Overview (Preview) - Microsoft Fabric | Microsoft Learn

NOTE: These are premium connectors so ALL your Power App users need a Premium license.

Re: Connecting a Power App to a Fabric warehouse repository

pmscorca — Mon, 03 Feb 2025 08:25:06 GMT

Ok. It is possible to write data on a Fabric warehouse, ok.

But the question is another one.

Is it possible for a Power App reading from and writing to a Fabric warehouse directly without any intermediate data passages, please? Thanks

Re: Connecting a Power App to a Fabric warehouse repository

nilendraFabric — Mon, 03 Feb 2025 08:32:10 GMT

Hello pmscorca

The SQL analytics endpoint in Microsoft Fabric’s Warehouse supports read and write operations, unlike the SQL endpoint associated with a Lakehouse, which is read-only.

Please give this a try. This is supported iin MS Fabric currently capabilities:

1. Direct SQL Connectivity:
• Use Fabric Warehouse’s built-in SQL analytics endpoint (T-SQL compatible) with Power Apps’ SQL Server connector for read operations.
• Write data via stored procedures executed from Power Apps, bypassing Dataverse entirely.
2. Power Automate for Complex Writes:
• Trigger flows from Power Apps to run dynamic SQL queries (INSERT/UPDATE/DELETE) directly against Fabric Warehouse.
3. Stored Procedure Migration:
• Migrate SQL Server stored procedures to Fabric Warehouse after adjusting unsupported syntax (e.g., collations).

This approach won't need dataverse for data storage.

Thanks

Re: Connecting a Power App to a Fabric warehouse repository

pmscorca — Mon, 03 Feb 2025 09:50:51 GMT

Hi, thanks for your reply.

I'd like to understand better.

For writing data to a Fabric warehouse I could use the SQL Server connector of Power App, and from the Power App I could run a stored procedure having a INSERT/UPDATE/DELETE operation or launch a flow, isn't it?

Using a flow or Power Automate could cause low performance and perhaps also running a stored procedure.

Is it possible to execute a direct INSERT/UPDATE/DELETE operation using the SQL Server connector? Thanks

Re: Connecting a Power App to a Fabric warehouse repository

nilendraFabric — Mon, 03 Feb 2025 09:57:01 GMT

Hello pmscorca

Yes, you can write directly to Fabric Warehouse from Power Apps via the SQL Server connector under these conditions:

• Requires tables to have enforced primary keys .
• Use Power Apps formulas like `Patch()` or `Remove()` for single-row operations.
Stored Procedures Execute faster than Power Automate and avoid flow latency
use Power Automate for complex/bulk operations or tables without primary keys (adds ~1–2s latency) .

please accept this answer ans give kudos is this is helpful