Occasionally a new row with only users email is added at the bottom of the user profile (google sheet), which creates problem.
The user already exists in the user profile.
Allow user to edit is not on.
It is not a Google account.
I have noticed in the App:Logins that the user has logged in several times within same hour.
The names shown there (that’s the email column) are all duplicates of existing users.
There are no formulas anywhere in the Google Sheet.
I was trying to find a correlation between this and App: logins, but couldn’t see anything obvious. It’s a little difficult because these “phantom rows” have no timestamps.
I also did a “Find all uses” on the email column. There is only one action in the whole app that adds a row to the table - when a new user is created (it’s a Private Pro app).
That is weird. My first though for @Ralf would be to double check to make sure that there are no other actions in the app that may be adding a row. Probably not the case here, but always good to double check.
My only other thought, is that I wonder if for some reason the data isn’t completely synced between glide and google when the user signs in, and for some reason glide didn’t know an existing row existed, so it created a new one.
Maybe a temporary glitch with the connection between glide and google??? I think I’ve seen some other post with people having issues signing in, but it didn’t seem to be widespread, so maybe something was going on.
Yeah, it is weird. I’ve never seen anything like this before.
In my case, this is an app I built for a client and they went live with it a couple of weeks ago. Prior to going live, there was at least about a month of quite intensive testing and I never saw anything like this. And the app hasn’t been touched since they went live, so I was quite surprised to find this yesterday. The good news is that there didn’t appear to be any negative impact on the app performance, and there were no issues reported from users. Row Owners are applied to the User Profiles table, so I suspect these extra rows were just being ignored. I did a scan of the generated RowID’s, and couldn’t find them being referenced anywhere else.
Yeah, that seems the most likely explanation. For now, I’'ve just removed the extra rows and will keep an eye on it for a few days.
Actually @Jeff_Hager - just another thought. In recent times I’ve been finding that occassionally when I open an app in the builder all data will load, except for the User Profiles table, which remains empty. When this happens, I usually have to exit the app and then open it again and then it loads. Have you noticed this behaviour? I wonder if it’s related…
Yeah, that’s not good at all.
I’m not sure if you do this, but when using importrange it’s always a good idea to keep your column headers static, and start the importrange from the second row. This helps to minimise the damage if the importrange ever breaks, as any Glide computed columns will remain intact.
Hard to say. If you see a bunch of App: login records, then it’s possible that they were having problems signing into the app at the time, or something wasn’t working for them when they attempted to sign in. Might be worth reaching out to the users to see if they experienced any problems.
No, both apps creates these rows.
Members Register app creates the rows at the end of the sheet, the sub app creates the rows below the the importrange, which ends at row 1500.