App is public with required sign-in. Sign up screen is submitted from a “set column values” action that includes default values needed by the app.
How can I prevent a new user from using/inputting an already in use phone number.
The submit button on an “set column values” action does not have “allow actions” conditions.
Are you using Row Owners in your User Profiles table? (assuming that the Phone number is stored in that table)
For the majority of columns yes..(including phone)
It still allows the new user to complete their profile, it just does not record the phone number in the user table.
Not sure what you mean by that. When Row Owners are set, they apply to all columns. The reason was asking is because if you are using Row Owners, then there is no easy way to check if a Phone Number is already in use. You would basically need to maintain a separate list of the numbers of all users somewhere that isn’t subject to Row Owners. And then of course you have the problem of matching numbers. Any given number can be written in many different ways. Take for example the US number: 212-456-7890. That could be written as:
All valid variations of the same number. So it gets a bit tricky.
In these cases, I would use Numverify’s API to get a standardized number (and also validate the number).
They give you 100 free API calls per month.