Hi Dani,

I was able to reproduce the behavior you reported, and the filtering is the same for multiple users.

It can be cleared by using the filter icon in the right upper of the widget, and selecting "clear all filters”.

With kind regards,

Chris.

In order to get the facts straight, or as straight as possible, I think we need to get  a grip on the scenario for which the ‘persistence’ happens.

Dani talks about ‘sessions’, not necessarily ‘users’. So making it more explicit: he seems to get the filter settings, for a table, when returning to the app later on.
I do not actually think he means that other users (on other devices, or using a really different Windows/user login on a device) get the same filtering as he applied himself.

Can you verify this for me, @danileidelmeijer ?

Just to clarify why I think this would then be ‘expected behaviour’:

• WebUI apps on PRO do not, by themselves, save their state back to the server. (technically: the webui.json file, which contains these filter settings is never sent to the server)
• Their state is however stored in Local Storage of the browser. Which does not expire when logging out or closing the tab.
• The stored information is keyed by app name and version. There is no user information to make them unique, because we expect that the browser that can access this local storage is used by one app user only. Other users are assumed to use fully different machines, or use different machine accounts (which separates browser storage).

So @Chris Kuip , if you were logging in to the PRO portal with different portal account users, launching the same app in the same browser, even across multiple tabs, they would all be able to read the Local Storage, which will have the same table filtering for all of the ‘sessions’. Not stored on the server with the app, but all locally and all accessible by that one browser that you are using.

And if you were to ask a colleague to launch the same app, but of course from their own machine, you’d see that they will not have your filtering applied.

And, if Dani’s model _really_ would seem to persist table filtering across different users on different machines, then the model/app itself must be doing something to store that on the storage options an app on PRO has. But not by default. Dani has not told us if his model might be doing something like that.

I hope this explanation about the technique and the difference between sessions and types of users, makes sense of what is happening. By design.

@Chris Kuip @Edo Nijmeijer “I do not actually think he means that other users (on other devices, or using a really different Windows/user login on a device) get the same filtering as he applied himself.”

→ True, the filtering is only visible for myself and it persists through AIMMS PRO sessions (so after the active data session has closed). 

Thank you for explaining the behavior and good to know it is by design.