Upon clicking on a collection item, I essentially go to another page with a dynamic ID in the url.
Then, this ID is being used by a collection to fetch only the current selected user.
But, the ID and the collection’s result are out-of-sync when doing that multiple times in the same session. Refreshing fixes the issue and reload the proper user’s info.
I’m not sure if it’s a bug, a race condition, or something I did wrong.
Video:
https://watch.screencastify.com/v/aYvsae4WGVBPvv2blPXZ
From what I can tell, you did nothing wrong 
Just asked the tech team to look into it.
Any news? I didn’t find a way to fix that, yet.
It has been added to the developers’ roadmap but yet to be started.
@Joyce I need a solution, it’s been 2 weeks, my client isn’t happy 
Any workaround?
Can you call the action fetchCollection after you updated the currentUser variable ? Your collection filtering on the id should be up to date and the page displaying it too, you can call it on page load after the redirection for example
@Alexis I don’t “update” the currentUser variable, it’s provided by WeWeb automatically.
But I managed to do something like that at the page level. 
I wish that wouldn’t be necessary, I’ll need to do it for all of my pages one by one.
But better than before!
