| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3956 |
| Technical Name |
docuware_masterdata |
| License | LGPL-3 |
| Website | https://www.codebar.ch |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3956 |
| Technical Name |
docuware_masterdata |
| License | LGPL-3 |
| Website | https://www.codebar.ch |
DocuWare Master Data
Synchronize Odoo master and reference data into DocuWare data-record cabinets.
codebar Solutions AG
docuware_masterdata pushes Odoo master data into
DocuWare data-record cabinets via the DocuWare Platform REST
API. The administrator points the module at any Odoo model,
picks a cabinet, and defines the field-by-field mapping
per target — no code-based mapping registry. Default
sync targets are seeded (inactive) for Contacts and, when
the Accounting app is installed, for Chart of Accounts,
Taxes and Journals. It does not push documents, attachments,
or invoices.
What’s in the box
Three sync strategies
full_dump, incremental_upsert
(default), or incremental_mirror. Pick the right
trade-off between speed and authoritative deletes per target.
Composite record keys
Tick one or more mapping rows as Identifier;
their values are JSON-encoded into the DocuWare record key
(e.g. {"VAT": "DE123â¦", "COUNTRY": "DE"}). Mix
record, company, user
and database sources to keep multiple Odoo
tenants or companies sharing one cabinet collision-free.
Disabled by default
The daily cron and the seeded default sync targets are inactive on install. An administrator must explicitly configure each target before any data leaves Odoo.
How it works
-
Configure a connection in
DocuWare → Connections
(provided by
docuware_authentication). -
Open DocuWare → Sync Targets. Default targets
are pre-seeded (inactive) for Contacts
(
res.partner) and — when the Accounting app is installed — for Chart of Accounts (account.account), Taxes (account.tax) and Journals (account.journal). You can also create a target for any other non-transient model. - On each target, set the DocuWare connection, pick the file cabinet from the dropdown (the list is populated by clicking Sync on the connection, which caches cabinets and their index-field schemas), define the field mapping with at least one row ticked as Identifier, choose a strategy, and refine the filter domain if needed.
-
Tick Active and click
Run sync now. With OCA
queue_jobinstalled, the job runs asynchronously on theroot.docuwarechannel; without it, the call runs inline in the request thread. - Watch DocuWare → Sync Log for results, and use the Synced records button on each target to drill down per record.
Requirements
- Odoo: 19.0
-
Odoo modules:
docuware_authentication(pulled in automatically) with a working DocuWare connection. The Accounting app (account) is optional — install it to unlock the Chart of Accounts, Taxes and Journals seeded targets. - A DocuWare tenant with one or more data-record file cabinets, exposing the index fields you intend to map.
- Optional: OCA queue_job with a running worker for asynchronous sync execution. Without it, syncs run inline in the request thread — fine for small deployments; use it for high-volume workloads.
Strategies
full_dump
Re-pushes every matching record on every run. No deletes. Use for small datasets or periodic full resets.
incremental_upsert
Pushes new and changed records (by write_date).
No deletes. Safe and fast — the recommended default.
incremental_mirror
Upsert plus deletes in DocuWare for records no longer in Odoo. The form shows a warning banner when this strategy is active. Use with care.
Permissions
-
docuware_masterdata.group_docuware_masterdata— full CRUD on sync targets and links; read access on connections and the sync log. Members can configure and run master data syncs without the DocuWare Authentication group. -
The synced model is read with the configuring user’s record
rules — a sync never pushes records they could not read.
Link, log and token writes use
sudo(), so the user does not need write access on those internal tables.
Setup walkthrough
Open sync targets, configure the cabinet and field mapping, run a
sync, and review the log. Ensure docuware_authentication
is connected first.
Sync targets
DocuWare → Sync Targets — seeded defaults (inactive) plus any custom model targets.
Target configuration
Connection, cabinet, identifiers, mapping, strategy and domain.
Run sync
Activate the target and use Run sync now.
Connections
DocuWare → Connections (from
docuware_authentication).
Sync log
DocuWare → Sync Log for run results.
License & support
Released under LGPL-3.0-or-later .
Built and maintained by codebar Solutions AG. Support: helpdesk@codebar.ch.
Privacy: see codebar.ch for our data protection notice.
Please log in to comment on this module