Greetings. There is a significant need in PBI Embedded for a built-in "Export Triggered" event handler like there is with data selected and button clicks (examples of Embedded events).
Problem Statement
The Microsoft Export data option is invaluable for embedded scenarios, but not having the ability to capture when a user performs an export app-side introduces several problems.
- Audit/Compliance Risk: In App Owns Data scenarios, the audit logs only capture service principal, so customers have zero ability to track which user performed an export. Having an event handler would let us log this app-side and correlate via activity ID.
- Activity Tracking/Limited Customization: Customers may want to trigger an event when a user exports (e.g., send email, log action, display toast message), and the lack of an Export event handler on the native Export function prevents this.
For customers dealing with sensitive data or heavily-regulated industries that want/need to use App Owns Data, this forces them to have to pay developers to create a custom Export experience.
Summary
Please add an "Export Triggered" event handler. Having this functionality would unlock several capabilities with PBI Embedded and also make it easier/more cost-effective for customers wanting to use App Owns Data to leverage PBI Embedded.
on:
Add a Git-tracked “resources” folder to Lakehouses
on:
Add native Dev/Test/UAT/Prod semantic model compar...
on:
Computed Columns in Fabric Data Warehouse
LiLiu_Fabric
on:
Deployment Pipeline Run in Fabric monitor