Rekhu Builder for Odoo runs your imports itself
Rekhu Builder 1.0.8 brings a file from your project into Odoo and runs the import wizard it built, a dry run first, so you answer yes in the chat instead of clicking through the steps.
Rekhu Builder could already build an import: a module with a wizard that reads an export from SnelStart, Exact or another package and turns it into contacts, accounts and opening balances. Then it handed you a list of clicks: open the wizard, choose the list, upload the file, press Import, send back the report.
Rekhu Builder 1.0.8 does those steps itself.
How it goes
You put the export in the project's Files panel and ask for the import. The builder then:
- Brings the file into Odoo. The file goes from your project's Files panel to the database as an attachment.
- Runs a dry run. It asks first, then fills in the wizard with its settings and the file and presses its button. A dry run changes nothing.
- Shows you the report the wizard wrote: how many records, what it would create, what did not match.
- Runs the real import after your second yes.
On staging and production every step waits for your yes in the chat. On production it stays off unless you allowed changes there.
What it may and may not do
The builder calls a model's public methods, the way a button in Odoo calls them. It does not change modules that way (it upgrades those as before), nor settings, users or access rights, and it never deletes records through a call.
Data an import brought in is not part of the builder's undo, which covers files and modules. That is why every import starts as a dry run.
Also in recent releases
- 1.0.7: the builder restarts Odoo itself when new Python must load, after your yes. See the article about it.
Update the module from the Rekhu for Odoo page.