Import Res ID
Adds a Document XML ID field, res_external_id, to messages (mail.message) and attachments (ir.attachment), to link them to their document by the XML ID of that document.
Messages and attachments point to their document with a model name and a database id, which an import file cannot know. With this field, chatter messages and attachments can be imported for records imported earlier.
Table of contents
Use Cases / Context
When migrating to Odoo, the history of the records, the chatter messages and the attachments, has to be imported too. Without this module the import file needs the database id of every document, which is only known after the documents are imported.
Usage
Import messages or attachments with a res_external_id column holding the complete XML ID of the document, as module.name. The model and the id of the document are set from it:
body |
message_type |
res_external_id |
attachment_ids/id |
|---|---|---|---|
<p>Called the customer</p> |
comment |
legacy.partner_42 |
legacy.attachment_7 |
The field can also be given to create() and write(), and is filled in exports with the first XML ID of the document.
An XML ID that does not exist stops the import with an error, instead of creating a message or attachment that is not linked to anything.
The usual access rights apply to the document. Only administrators can move an existing message to another document.
Import the attachments first, linked to the document with res_external_id, then the messages that refer to them with attachment_ids/id.
When importing a history, import the documents themselves with "mail_create_nolog": True or "tracking_disable": True in the context, so that Odoo does not add a created message of today next to the imported messages. Messages keep the date and author_id of the import file. To also keep their create_uid and create_date, use the import_metadata module.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
bosd
Other credits
Based on the idea and the res_external_id field of the import_res_id module of easier_import by Thibault Francois. This is a new implementation.
Maintainers
This module is part of the GetFluvo/addons project on GitHub.
You are welcome to contribute.
Metadata
Release files for odoo-addon-import-res-id 19.0.1.0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_import_res_id-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_import_res_id-19.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_import_res_id-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_import_res_id-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19363630c2b1db12c9f15290bdd3de1cc22aedfe70bc4d3fb483f9f80368f2a0
|
|
BLAKE2b-256 checksum How to use checksums |
96eefb6c9276abe2dd853a26f90009eb1a9c3a752c6356c22df76225f224da7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logSecurity for odoo-addon-import-res-id 19.0.1.0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for odoo_addon_import_res_id-19.0.1.0.0.2-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.