Writeback solution in Microsoft Fabric using a Lakehouse table but facing the issue

Hi Shubham_rai955 

Direct writeback to a Lakehouse table from Power BI (or any client app) is not supported natively yet, because Fabric Lakehouse tables are designed for analytical (read) workloads  not transactional updates.

However, you can achieve controlled writeback using one of the following supported patterns:

What You Can Do

1. Use a Fabric Notebook or Data Pipeline
   • Create a notebook or pipeline with an UPDATE / MERGE SQL statement.
   • Trigger it from Power BI using a Power Automate button or flow.
2. Use a Staging Table
   • Send updates to a separate table (via PowerApps or flow).
   • Periodically merge those into your main Lakehouse.
3. For Real-Time Writeback
   • Use Dataverse or SharePoint List >> supports instant updates.
   • Then sync that data back to Fabric if needed.

If It Still Doesn’t Work

• Check your user’s Fabric workspace permissions (need Edit + Contributor).
• Ensure the Lakehouse table is Delta format (required for MERGE).
• If Power BI >> Automate >> Fabric call fails, test the notebook manually.
• Last option: store edits in Dataverse/SharePoint and rebuild pipeline logic.