Hi everyone,
In my app, I’m using a Form Screen where users enter their information.
- When a new row is added to Table A (with Email and some details),
- I’d also like the same information to be added to Table B.
- However, if the email already exists in Table B, then I don’t want to create a duplicate row there.
- Table A should always save the new row.
Is there a good way to structure this workflow so that duplicates are prevented in Table B but Table A continues to collect all submissions?
Thanks in advance for your suggestions!
You could use query column to get the rows where email is current email field (I suggest you to make your form in a helper table). If is empty, then you can add it.
1 Like
May we know the use case for adding some sort of the same info for table B? We might be able to suggest an alternative in data structure for you.
1 Like
I’m building a reservation session, and I’d like the user data registered for that session to also be added to a User table that controls access to the page.
The user data consists of name, email, phone number, and team name .
1 Like
So is it correct to assume this is a public app and users are not required to log in at all?
1 Like