We have a form view with four cascading dropdowns .At first we are able to populate the value properly and move next.(Please refer to screenshot 1)
Once we Click on previous and come back to our original Screen with the above mentioned cascading dropdowns, we have applied a form refresh settings in our Flow Action to enable user to select any other value under that Cascading dropdown if required.(Please refer to screenshot 2)
Currently even after the user selecting new value, it still contains the old value which was selected earlier
As we debugged, On change refresh is not working as expected(please refer to screenshot 3)
I wonder if you might be seeing this known issue. Can you review this article and see if this could be the issue (if you see the double refresh pattern in the network trace).
We tried using Condition in stead of When rule , but still the issue is happening . So here , 2 level of refresh is happening ->one from Dpage context ( as we have used cascading drop down ) and one from Flow action refresh setting . Might be the sequence of the refresh is playing a role here , though not sure .
Are you seeing the double refresh type behavior as described in that article? If so then there is likely still something configured on the view using a when rule based condition (Visibility / Disabled / Required conditions), or a calculated field. If that is the case then you can try and stop the additional refreshes by switching to custom conditions, and removing calculated field from the view.
I would always recommend using a custom condition over a when rule for dynamic UI (as they are evaluated on the client side) unless you need to evaluate the condition on the server side. See - Conditional logic in Views
I would ideally like to see the network trace for the behavior, so you might consider opening an INC for us to investigate in more detail.
