Commit Graph

8 Commits

Author SHA1 Message Date
Radovan Skolnik
b77efdb3f6 [MIG] base_import_match: Migration to 13.0
[UPD] Update base_import_match.pot
2021-02-25 16:20:20 +01:00
Radovan Skolnik
e892b743d7 [IMP] base_import_match: black, isort, prettier 2021-02-25 16:20:16 +01:00
ernesto
5d9ab196fd [MIG] base_import_match: Migration to 12.0
[UPD] README.rst

[UPD] Update base_import_match.pot
2021-02-25 16:20:16 +01:00
Jairo Llopis
eaaaac1951 [10.0][MIG][base_import_match] Migration and update
Includes:

- Normal migration steps.
- Usage of brand new `_inherit = "base"` in Odoo 10, which implies
  removing a lot of monkey-patching code.
- Log a warning when multiple matches are found.
2021-02-25 16:19:31 +01:00
cubells
82a31630fb base_import_match module 2021-02-25 16:19:31 +01:00
Jairo Llopis
82bb1e33a3 Avoid UnicodeEncodeError. (#544)
* Fix wrong README format.

* [FIX][base_import_match] Avoid UnicodeEncodeError.

When the model or field you chose was translated and had some non-ascii
character, you got an error like this: `UnicodeEncodeError: 'ascii' codec can't
encode character u'\xed' in position 15: ordinal not in range(128)`.

Now, using unicode strings, that won't happen again.

* Do not require a hidden field.

* Further unicode protection, add ondelete clause.
2021-02-25 16:19:31 +01:00
Jairo Llopis
bdfc921a2e base_import_match: Add conditionals to fields when importing.
This patch allows to import res.partner records by VAT when is_company==True by default.
2021-02-25 16:19:31 +01:00
Jairo Llopis
0757f3c2bc base_import_match: Import deduplicator.
By default, when importing data (like CSV import) with the ``base_import``
module, Odoo follows this rule:

1. If you import the XMLID of a record, make an **update**.
2. If you do not, **create** a new record.

This module allows you to set additional rules to match if a given import is an
update or a new record.

This is useful when you need to sync heterogeneous databases, and the field you
use to match records in those databases with Odoo's is not the XMLID but the
name, VAT, email, etc.

After installing this module, the import logic will be changed to:

1. If you import the XMLID of a record, make an **update**.
2. If you do not:
   1. If there are import match rules for the model you are importing:
       1. Discard the rules that require fields you are not importing.
       2. Traverse the remaining rules one by one in order to find a match in
          the database.
          1. If one match is found:
             1. Stop traversing the rest of valid rules.
             2. **Update** that record.
          2. If zero or multiple matches are found:
             1. Continue with the next rule.
          3. If all rules are exhausted and no single match is found:
             1. **Create** a new record.
   2. If there are no match rules for your model:
      1. **Create** a new record.
2021-02-25 16:19:31 +01:00