I created a backend and an API that I bring into Adalo as an external collection (this feature is awesome once I understood how to use it). So the only collection I’m using Adalo for is the Users collection. I use the currently-logged-in user’s email address as their primary identity and I fetch external collections based on that. However, I ran into a pretty big problem.
After creating a new account, I immediately fetch associated collections for the user. I’ve noticed that this initial request doesn’t populate the user email field. Here’s an example from my server:
As soon as I reload the page or log out/log in, then this “owner_member_email” value is populated, but it isn’t populated immediately after a newly created user lands on the page (as the default action after account creation). I can work around this for the moment as a new user doesn’t have any created objects yet, but I WOULD like to record the email of the user right after they create their account in Adalo. If this value is null then I can’t do that and I have to insert some “filler” page after account creation to give Adalo a chance to popular the field before invoking the API.
Have others seen this issue? Is this a known issue that’s on Adalo’s radar?