Environment context setup

By default, OdoMate builds and tests modules against a standard Odoo 19 install. If your database has other modules installed, custom fields, or settings turned on, a generated module can miss those — or collide with them. Environment context closes that gap: you upload a structural snapshot of your Odoo database once, and OdoMate uses it to write modules that fit what you actually have, and to test them on a replica built from the same module list.

Install the connector

Environment context comes from the OdoMate Connector, a module you install into your own Odoo database.

1. Open your Profile page and find the Environment context card.
2. Click Get the connector on Odoo Apps to open its Odoo Apps Store listing, and install it into your Odoo database like any other app.
3. In Odoo, open Settings ▸ Technical ▸ Export OdoMate Context and generate the snapshot.
4. Download the resulting odomate_context.json, review it, and come back to the Environment context card to upload it.

Note

The connector only exports structure — installed modules, models, fields and settings — never your business records, user data or credentials. Reviewing the file before uploading is worth doing the first time so you can see that for yourself.

Upload the snapshot

Click Upload snapshot on the Environment context card and choose the odomate_context.json you exported. OdoMate re-checks the file itself before storing it — it isn’t trusted just because it came from the connector — and rejects it with a specific reason if something looks wrong, so you know whether to re-export or report a problem.

Once it’s accepted, the card shows what OdoMate now knows about your environment: your Odoo version and edition, module and model counts, how many settings it saw, and how many custom fields and customized views it found. Modules are also broken down by source (core, OCA, third-party, your own custom modules, and so on).

Note

Uploading the same environment again — for example, re-exporting an unchanged database — is recognized as no change rather than stored as a new snapshot.

The snapshot applies to your whole team: whoever uploads it, everyone on the team generates against the same connected environment.

What connecting changes

Once an environment is connected, your next generation (not runs already in progress) is built against it instead of a vanilla Odoo assumption. OdoMate uses your real module and field list to avoid redefining something that already exists, and to depend on modules it now knows you have — including ones you installed yourself, from OCA, or from third parties. The sandbox you preview a finished module in is also built as a replica of your environment rather than a stock database, so what you click through matches what you’d actually get.

If the export is large enough that some detail had to be dropped to fit, the card tells you which sections were truncated, so you know the digest is incomplete rather than assuming it saw everything.

Replacing or disconnecting

Export a fresh snapshot any time your Odoo environment changes and click Replace snapshot to upload it — this works the same as the first upload and simply supersedes what was there.

To stop using environment context, click Disconnect.

Caution

Disconnecting deletes the stored snapshot. Future generations fall back to the standard Odoo assumption until you upload a new one — this can’t be undone, though nothing stops you connecting again later.

If the card instead shows a message that the snapshot can no longer be read, it was written by an older version of the connector than OdoMate now supports. Export a fresh one from Odoo and upload it the same way.