Share
Report
2Hi,
I am working on a proof of concept (POC) to integrate PowerApps with the Fabric Warehouse SQL endpoint. My client’s requirement is to update data in Fabric Warehouse tables using a SQL Server endpoint from PowerApps with a SQL Server connector.
Previously, I accomplished this using Power Automate to write a SQL query in a Power Automate action, and it worked successfully. However, the current requirement is to update the data directly using PowerApps. When I attempt to update the data from PowerApps using the Patch function, I encounter the following error: “The data source is either read-only or has no primary key, so the Patch function cannot write to it.”
Is there any way to achieve this? According to some blogs I read, “PowerApps can only write to tables with an enforced primary key.” It seems this is not possible with the current T-SQL layer in the Fabric Data Warehouse.
Could you please provide any ideas or solutions to address this issue?
I am working on a proof of concept (POC) to integrate PowerApps with the Fabric Warehouse SQL endpoint. My client’s requirement is to update data in Fabric Warehouse tables using a SQL Server endpoint from PowerApps with a SQL Server connector.
Previously, I accomplished this using Power Automate to write a SQL query in a Power Automate action, and it worked successfully. However, the current requirement is to update the data directly using PowerApps. When I attempt to update the data from PowerApps using the Patch function, I encounter the following error: “The data source is either read-only or has no primary key, so the Patch function cannot write to it.”
Is there any way to achieve this? According to some blogs I read, “PowerApps can only write to tables with an enforced primary key.” It seems this is not possible with the current T-SQL layer in the Fabric Data Warehouse.
Could you please provide any ideas or solutions to address this issue?
Thanks!
Categories:
I have the same question (0)
All responses (
Answers (
