Forum Discussion
Writeback Functionality In Power BI
Option 1) Put an API layer in front of the stored procedure:
Power BI triggers an action → that action calls an HTTP endpoint → the endpoint runs the stored procedure and returns success/failure.
Typical implementations:
Power Automate button in the report → calls an API / SQL connector → runs the SP.
Power Apps visual → user submits the “key” → Power Apps calls SQL / API → runs the SP
Option 2) Translytical Task Flows (write-back/actions):
If your write-back can be implemented through Fabric user data functions (or you can expose your SP via an API that the function calls), you can put a “data function button” in the report that passes inputs (like your key) and triggers an action.
Super UserOption 1) Put an API layer in front of the stored procedure:
Power BI triggers an action → that action calls an HTTP endpoint → the endpoint runs the stored procedure and returns success/failure.
Typical implementations:
Power Automate button in the report → calls an API / SQL connector → runs the SP.
Power Apps visual → user submits the “key” → Power Apps calls SQL / API → runs the SP
Option 2) Translytical Task Flows (write-back/actions):
If your write-back can be implemented through Fabric user data functions (or you can expose your SP via an API that the function calls), you can put a “data function button” in the report that passes inputs (like your key) and triggers an action.
Community SupportHi bharathi2233
Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.