So I have an app where a new user gets sent into a form as their landing page. When the new user logs in, it takes a while before the records appear in the Glide users table. This results in the input fields not displaying on the view, although the user was already navigated. It takes up to 30 seconds before the new user gets to see which input fields they can fill.
I am handling this a bit with visibility conditions. I show a message ‘We are collecting some data for your user…’ but many users will not understand what is going on when it takes 10+ seconds for the relevant content to load. It is very important for us that we do not lose leads in this step.
Also, I would like to note that this issue occurs at random. When I am testing this, issues appear irregularly.
That’s weird, since Glide Tables would provide the best experience. Would you mind giving us some screenshots of related tabs’ configurations, or a video?
I did it in this way. Just chekking if the ID of the user exists. So just checking if the row exists in the DB. This is the visibilty I have on the fallback I was talking about. On the container for the form i have no visibility condition
I have just tried with the visibilty to check the email. But the same is happening.
I just did a test with a collegue. and was +10 seconds for inputs to appear.
My user table has 93 columns, but ± 60 of them are a lookup. Could this cause an issue regarding this?
How many of those lookups are used in that very first screen?
– 14 to be exact. I use it render my content in multiple languages.
I notice that you are using Big Tables. Are any of the Lookups (especially those that are used on the first screen) referencing Big Tables?
– No, for my language table I used a Glide table. There are relation columns that link with bigtables tho. But these are empty in my first screen. Could an empty relation cause it?
