Does Appsheet have an in-built elegant way to enforce a one-to-one data relationship constraint (to follow the database design)?
I have searched long and hard and it seems people are hacking a solution by setting the Foreign Key field in the child table (Appsheet settings) as the Primary Key for that table.
Works, but seems inelegant with possible confusion re table design down the line.
Is that the only way?
We also tried data validations -
This one worked for creation of new records:
but unfortunately it also prevents you from editing an existing record of course…
Perhaps someone else has a cracked a better data validation formula that can also work on editing a record?
Or I’ve missed the right way to enforce database table relationships in Appsheet?