When a user wants to add info to a client record, they should first search for that client. I am afraid that they will skip the search and create the client record, resulting in a duplicate record. I want to prevent this.
The best way would be to be able to define a primary key, and Tape validating a new record against this key. Today, it is possible to define a field to be required, but not to be unique. Having a unique key for a record would be perfect (and actually, quite normal for a database system to have).
The second best way would be to have a validation trigger at field level. It should fire when a field value is entered, and must be able to alert the user. This cannot be done with an automatoon on the event when a record is created, because it fires after the record is created, ánd is not able to present an alert to the user.
This would definitely be a fantastic extension of Tapes’ functionality!