Hello, I think Iâm having the same problem that Renaud is saying here. Hereâs how I am replicating the bug each time:
Iâm using an external collection (airtble database) and have made a custom list. I have set a filter on the list to show only specific records from my database. Iâm using a filter which connects to a property of the user, say â{user_designation}â = âexecutiveâ where the âexecutiveâ value is pulled from the userâs login input via magic text.
In the mobile app, when I load the screen with this custom list, in the beginning all the records in the list is displayed, which quickly corrects itself after approximately one second to show only the filtered records. On desktop, if I recreate the same list with the same set of database and filters, all the records show up but they donât go away after 1 second. They remain there until I perform any sort of action or click a button (this could be clicking on a link and going back, clicking on a button with a âblankâ action, etc.). This is frustrating because it opens up the possibility of the user accessing information theyâre not supposed to, on the desktop app. They can also do the same in the mobile app, if they click on an item on the list before the filter kicks in, but Iâm at least trusting that they wonât be fast enough.
Please note that this only happens if I set the filter to query from Adaloâs database via a magic text. If I set the filter to simply as {user designaton} = âexecutiveâ then this doesnât happen
I donât really understand the solution.
I need to create a blank screen before make a redirection to the page ?
Because this happen only if the user refresh the page
I found a better solution than the above workaround, that Iâve now mentioned in that thread. This eliminates the need for having an input field altogether, and works 100% of the time, even after pressing F5 on a page. This is based on an observation that running any action triggers the filter to âreadjustâ and work properly.
What you need to do
So what you need to do is add a âblankâ action in the screenâs properties (e.g. âChange input valueâ but keep the fields empty; see the image below), and this triggers the filter to run correctly whenever the page loads. It does add a jarring stutter every time you transition back and forth the page though, so you can disable screen transition animations since they arenât used that much in web apps anyway
Hello, Iâm looking to understand screen transitions better. Could I ask please, where is the setting to disable screen transition animations.
Separately, when setting a screen transition to Push or to None, does that choice control just the visual effect in how the new screen is rendered, or does it control other things as well, like data passed to the new screen or other parameters.
(Iâm not seeing a description of this in the Adalo training, hope I didnât overlook something obvious.)
To disable screen transition animation, I just set the screen transition to None.
As for your second question, it only controls the visual effect on how the screen is rendered, nothing else. The data is passed normally and is not affected