Automatic History Tracking for Imports
by Viindoo
| Lines of Code | 402 |
| Technical name | viin_base_import_tracking |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/17.0/viin_base_import_tracking |
| Read description for | v 15.0 v 16.0 v 18.0 |
| Required Apps | Discuss (mail) |
An import that leaves a trace on every record it touched
Data imported through the standard import tool is written with tracking on, so each record's chatter shows what the file changed.
Automatic History Tracking for Imports (technical name viin_base_import_tracking) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for data owner, consultant, auditor, support.
At a Glance
The facts of Automatic History Tracking for Imports, version 0.1.0, in one place. Published by Viindoo.
How It Works
Import as usual, then read the record.
The record says what the file changed
The chatter entry carries the fields the import wrote, with their previous values.
Across the data you imported
Any model with a chatter and tracked fields records its own share of the import.
What You Get
Tracking left on while the standard import tool writes
Old and new values in the record's own chatter
The user who ran the import, on every record it touched
Works for creation and for update imports
Nothing changes about how you import
No separate log to consult
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Contacts
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
A field nobody declared as tracked is still silent - which is why change-tracking apps matter.
That is the price of the trail; import in batches you would want to audit.
It tells you what happened; reversing it is still your work.
The record records its own change, not the spreadsheet.
Works Well With
Apps from the same stack, built to fit this one:
Contact Change Tracking
Tracked fields on contacts, so imports have something to record.
to_partner_track_changeWho Should Use Automatic History Tracking for Imports?
Data owner
Can tell an import from a typo, months later.
Consultant
Proves what a migration file actually changed.
Auditor
Reads master-data history that includes bulk changes.
Support
Finds the import behind a value nobody recognises.
Frequently Asked Questions
What does Automatic History Tracking for Imports do?
Data imported through the standard import tool is written with tracking on, so each record's chatter shows what the file changed.
What does Automatic History Tracking for Imports not do?
Only tracked fields leave a trace. A field nobody declared as tracked is still silent - which is why change-tracking apps matter. Large imports produce large chatters. That is the price of the trail; import in batches you would want to audit. It does not undo an import. It tells you what happened; reversing it is still your work. It does not log the file. The record records its own change, not the spreadsheet.
Who is Automatic History Tracking for Imports for?
Data owner: Can tell an import from a typo, months later. Consultant: Proves what a migration file actually changed. Auditor: Reads master-data history that includes bulk changes. Support: Finds the import behind a value nobody recognises.
Which Odoo version and editions does it support?
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: mail, base_import. Odoo installs them with it.
How do I set it up?
Import as usual, then read the record.
What works well with it?
Contact Change Tracking (to_partner_track_change): Tracked fields on contacts, so imports have something to record. Employee Change Tracking (to_employee_changes_tracking): The same for HR data. Document Management (viin_document): Where the import file itself can be filed.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_base_import_tracking; pre-sales questions go to sales@viindoo.com.
See Automatic History Tracking for Imports in Action
Live demo: v17demo-int.viindoo.com/web#action=base.action_partner_form
Need help with Automatic History Tracking for Imports?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: apps.odoo.com/apps/modules/browse?author=Viindoo
Technical Requirement
Changes log
0.1.0 - Latest on the 17.0 line
- Tracking is enabled around the import execution itself, so both created and updated records record their changes.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.