Welcome!

This community is for professionals and enthusiasts of the Genio platform.
Share your questions and challenges, and help your partners!

0

0
Rodrigo Serafim
On 11/22/19, 11:47 AM

Why would you delete the previous record with the same unique code when you can just edit it?

Assuming the properties you printed belong to the CODE field, with 'Zero on duplicate' ('Apaga ao duplicar') you are specifying that the CODE field is to be cleared in the record you create from using the 'Duplicate' action on records. It has no effect on new records that have simply been inserted.

Deleting records is a really bad practice that usually just leads to even bigger problems like unwanted data loss, orphaned records and data fragmentation.

Find a way for the user to search if the record already exists before creating a new one. The 'non duplicate' validation will already warn the user they cannot save a duplicate record, so you just have to provide the next step for him: navigate to it.



0
José Gomes
On 11/22/19, 10:57 AM

When you duplicate a record, it´s mean that you are creating a new record using data from a existing record, there is no relations between those records. 

You can ignore data from source record (it will be empty or null), but you can´t create e new relation or delete a records because you are creating a new one.



Keep Informed

About This Community

This platform is for beginners and experts willing to share their Genio knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers. Read Guidelines

Question tools

13 follower(s)

Stats

Asked: 11/20/19, 1:53 PM
Seen: 40 times
Last updated: 11/22/19, 11:47 AM