[Andreas Dallner]

3 months, 3 weeks ago #70704

Up

1

Down

::

Hi Leonid,

Do I understand correctly that your issue is not a duplicate process, because the user double-clicked a button, but you are navigating the user, and the data there is still as before?

Why am I asking? If the cause is a double click, you need to implement a throttle technique. Disabling the button via UI-Action or using the busy indicator has small delays that do not help here. We had already had such cases. That is why Lukas created this idea: https://ideas.simplifier.io/ideas/PROD-I-518

What can you do if my assumption is correct:
As Lukas already wrote, you need to reset the data/reset the selected items before navigating back to the screen. As long as the table is not destroyed, UI5 keeps the selection info until you remove it: https://sdk.openui5.org/api/sap.m.ListBase#methods/removeSelections.

Have you also checked the rememberSelections property of the table, which prevents the table from resetting the selection even if there are binding changes if active?

If this does not help you, you should book an enabling session with our Customer Success Team. In that case, they can look into your implementation in detail and help you fix the issue.

PS: In any case, cookies do not have anything to do with it, as long as you do not use them explicitly to persist the checked items

Kind regards,
Andreas