Difference between revisions of "Features/Duplicate prevention"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
Example: | Example: | ||
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate. | |||
== How to do == | |||
* Entity: Check for duplicates | * Entity: Check for duplicates | ||
* Field: Is part of a unique key | * Field: Is part of a unique key | ||
Note checks realtime when entering data | Note checks realtime when entering data | ||
Revision as of 15:27, 24 August 2023
What it is
Example:
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.
How to do
- Entity: Check for duplicates
- Field: Is part of a unique key
Note checks realtime when entering data