-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
Category
- Question
- Typo
- Bug
- Additional article idea
Expected or Desired Behavior
no matter how an item gets selected, the onListViewUpdated callback should be triggered with the current selected item passed through the event parameter.
also the onExecute function should have the current selected item in the event parameter.
Observed Behavior
-from the second time and on when you select an item, onListViewUpdated is not triggered unless if the selection is done through the radio button. If you just click on a row the callback is not triggered.
-when you change your selection in anyway but through the radio button, when you click the extension button, the event parameter in onExecute contains the very fist item that was selected and not the current one.
So for example opening the context menu (which would select the item too) and clicking on the extension button would not trigger the onListViewUpdated from second time and on and onExecute will have the wrong item in event parameter.
I hope I'm doing something wrong, otherwise it's beyond me how this could not have been discovered in testing. We have deliveries for out customers soon and this would definitely put a stop to the whole project! We have flows and azure functions and an entire solution that all depends on this functionality to start the process. Should be able to get the selected item reliably.
Looking forward to an answer and hopefully a solution.
Hamed