Indeed expected behavior. Or let me rephrase, I do expect this behavior. As otherwise on each refresh of the enclosing object a database call would be made. Which is in my opinion something you don't want to have by default.
Seems you execute a microflow or nanoflow, which refreshes the enclosing object.
When using a nanoflow you could use the RefreshEntity action, to refresh the ListView entity.
Didn't use this myself yet, though worth a try.
Thanks for the feedback. I have been looking at this from different angles and indeed tried the “RefreshEntity” action as well, but nothing seems to refresh the list view as long as I use xpath as datasource.
This behavior is not really consistent with newer widgets it seems. I put a “gallery” widget on the same page and that does just refresh when I refresh the enclosing object.
It also seems inconsistent with using a microflow as a datasource in the list view, because then the list view does refresh.
I am going to take a step back and look at potential solutions / work arounds.
I am facing the same issue. Did you find a solution for this problem?
Thanks in advance!