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.
Recent ideas
Option to set custom width for gridlines OR fixed outer padding
When designing reports, using the align and distribute evenly options in the format pane are useful, however when designing report pages with fixed bleeds between visuals I have to follow these steps...IolaWhiteley1 hour agoAdvocate IINew2Views0likes0CommentsDefault Scrollable Time-Series Charts to Most Recent Data
Currently, Power BI time-series charts always open scrolled to the earliest (leftmost) date by default, which is inconvenient for reports where users are interested in the most recent (rightmost) dat...CStillwell2 hours agoNew MemberNew19Views2likes1CommentOption to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir13 hours agoMicrosoft EmployeeNew44Views10likes1Comment