Forum Discussion
JavaScript API - Data Selection Events - Catch Deselect Event
Hi,
great work with the JavaScript API!
With reference to Scenario 7: Data Selection in the Power BI JavaScript API demo.
We have successfully managed to embed our report and catch event.detail data after user click on the embedded power BI report.
However, we have not yet managed to catch deselect/unselect event to reset the in-page report filters. For instance, when you click directly on the bar graphs to filter the data, and then you click again on the same bar graph - the visuals are updated but not the data selected event...
Do you have any suggestion on how to catch this "deselect/unselect" event?
Thank you for your reply.
After I created this post we actually managed a workaround, almost by accident. We catched the "deselect" event by using the error handler event. See image, we get "error: CustomEvent", and inside the detail: Object we get a message saying "Could not serialize a data point."
Anyways, it would be very good with a detailed documentation update. As developers we spend a lot of time with trial and error.
4 Replies
JohnKris wrote:
Hi,
great work with the JavaScript API!
With reference to Scenario 7: Data Selection in the Power BI JavaScript API demo.
We have successfully managed to embed our report and catch event.detail data after user click on the embedded power BI report.
However, we have not yet managed to catch deselect/unselect event to reset the in-page report filters. For instance, when you click directly on the bar graphs to filter the data, and then you click again on the same bar graph - the visuals are updated but not the data selected event...
Do you have any suggestion on how to catch this "deselect/unselect" event?
That "reset" by clicking and clicking again seems just the Visualization interactions in a Power BI report. As per Handling Events page on github, it lists all events supported so far and there seems no such ""deselect/unselect" event.
The github documentation on the Power BI Javascript API is very limited, I'll escalate a content request internally and would share with you if there're more documents.Thank you for your reply.
After I created this post we actually managed a workaround, almost by accident. We catched the "deselect" event by using the error handler event. See image, we get "error: CustomEvent", and inside the detail: Object we get a message saying "Could not serialize a data point."
Anyways, it would be very good with a detailed documentation update. As developers we spend a lot of time with trial and error.
Hi, I'm having the same issue. Would you mind posting how you caught the event?
