Skip to content

Duplicates, merge and versions

  • Duplicates: a rule that warns or blocks when a record matches another one (same phone, email or name, normalized).
  • Merge: joins two repeated records into one.
  • Versions: in collections with versioning, a record keeps its earlier versions (v1, v2…) read-only, for example revised quotes.
  1. Go to Settings → Collections → the collection → Duplicates (Duplicados), turn on Detect duplicates, choose the fields of each criterion and what happens when a match is found (warn or block).
  2. To merge, open a record with possible duplicates, choose which one stays and confirm: the other goes to the trash and whatever pointed to it now points to the one that stays.
  3. Versions: on the record, New version (Nueva versión) freezes the current one (everything, header only or lines only) and the record continues as the next version. From the version list you can view an earlier one or go back to it.
  • Duplicates: 1 to 5 criteria of 1 to 4 fields. Phones without country prefix (504 by default), emails lowercased and texts without accents.
  • Merging requires delete permission on the collection.
  • Versioning is turned on in the schema (not on screen). It does not apply to configuration collections; line collections are versioned with their parent record.
  • A sealed record cannot get new versions. Versions require a connection.
  • find_record_duplicates: records that match one according to the rule.
  • merge_records: merges remove into keep.
  • list_record_versions, create_record_version and set_current_record_version.
  • The rule is set with patch_schema_draft → update_collection (duplicates, versioning); format in get_field_guide.