-
Goal: To use Row Actions to run an SQL Stored Procedure against the selected row
-
Steps: I added a row action that triggers a query that runs a stored procedure and references the selectedRowKey
-
Details: This is the first time this has happened the only difference is that I have expanding rows on the table I want to run this action from.
-
Screenshots:
In this image, I selected the row action for the 2nd row (blue highlight has moved), but the notification and the action are still stuck on the 3rd row.
Hi @Shegs,
Thanks for reaching out! I haven't been able to reproduce this bug Are you still seeing this issue? If so, could you DM me the app json or post screenshots of the row event handlers?
Yep,
same issue: notice the job number matches the one in orange, yet I clicked the row action for the one highlighted blue.
Here is the screenshot of that row action handler:
it calls a query that runs a stored procedure, but I use the confirmation message to make sure it's running on the correct one:
I tried recreating this issue on a new app using the Demo Data in a table that also expands and it seems to select the row first then trigger the action as it should. so I am not sure why.
I did create a JS Query that delays the row action by 300ms and that seems to work as a wait for the selection to change.
Hi @Shegs
Thanks for the screenshots! Glad you have a workaround
It's interesting that it works in a new table The same set up is also working on my side
Is this happening on stable 3.148?
If you can also share the app json, I can report it internally for a fix
3.148.3
I'll send you the JSON
Thank you! The export was very helpful. It looks related to the double click event on the table. If I remove the double click event, it starts working as expected (without the delay)
interesting.
I will keep you posted on a fix for this bug!