¶ Description
Upload Data to Odoo.
¶ Parameters
¶ Standard Tab
Parameters:
- Connection
- Login/user
Password - Database name
- Optional: extra parameters for cURL
- Number of retries on connection error
- Login/user
- Operation
- Table
- View fields names
¶ About
Create, update, or delete records in Odoo models (e.g.,
res.partner,sale.order) from your ETL tables.
OdooWrite authenticates to your Odoo server, maps incoming table columns to Odoo field API names, and executes one of three operations:
Create, update, or delete records in Odoo models (e.g.,
res.partner,sale.order) from your ETL tables.
- insert →
create - update →
write(requires recordid) - delete →
unlink(requires recordid)
Writes typically do not execute in Preview. Run the pipeline normally to commit changes.
¶ Prerequisites
- Odoo URL (your instance)
- Login/user, Password, Database name (DB) with permissions to the target model
- Network access to your Odoo host (configure a proxy only if your environment needs one)
¶ UI Map
- Login/user – Odoo username or email
- Password – Odoo user password (or an app-specific password if your setup requires it)
- Database name – Exact Odoo DB name (shown on the Odoo login screen)
- Optional: extra parameters for cURL – Advanced flags (e.g., proxy). Usually leave blank
- Number of retries on connection error – Default
5is fine - Operation –
insert|update|delete - Table – Odoo model (e.g.,
res.partner). Click the lookup button to populate the list after connection fields are set - View fields names (eye icon) – Opens a list of API field names for the selected model
¶ One-Time Connection Setup
- Enter Login/user, Password, Database name.
- (If you use a proxy) put your flag in extra parameters for cURL, e.g.
--proxy http://user:pass@proxy-host:8080 - Click Table → search to verify the connection; pick a model (e.g.,
res.partner).
¶ Field Mapping Rules
-
Your input table headers must use Odoo API names, e.g.,
name,email,phone,x_studio_custom__c. -
Provide only the fields you need to set. Odoo will apply defaults for the rest.
-
For update/delete, include column
id(integer record id). -
Booleans:
true/falseor1/0 -
Dates/Datetimes: ISO-8601 strings, e.g.,
2025-08-11or2025-08-11 14:30:00 -
Many2one (single relation): supply the integer id of the related record in that field (e.g.,
country_id=233) -
Many2many / One2many:
-
Supply an array of ids using Odoo XML-RPC array format (the connector converts it to the proper Odoo command under the hood).
Example for ids[4,5,6]:<array><data> <value><int>4</int></value> <value><int>5</int></value> <value><int>6</int></value> </data></array> -
For One2many where you create child rows, prefer creating children first and then link by ids; or use your ETL to build the array of existing child ids.
-
Use View fields names (eye icon) to confirm data types and API names for the chosen model.
¶ End-to-End Quick Start
- Prepare data (e.g., with an
InlineTableorreadCSV) using the API field names. - Set connection (login, password, DB).
- Pick Operation and Table (model).
- Run (not Preview).
- Check the log for per-row success/errors; verify in Odoo.
¶ Troubleshooting
-
Authentication error / Access denied
- Wrong DB name, login, or password. Verify on Odoo login screen
- User lacks model permissions (read/write/create/delete)
-
Unknown field/ValueError: Wrong value for ...- Column header must be the API name (custom fields end with
__corx_depending on your Odoo) - Invalid type (e.g., string where integer id is required)
- Column header must be the API name (custom fields end with
-
Many2many / One2many not applied
- Ensure the cell contains a valid XML-RPC array as shown above
- All ids in the array must exist and be readable by the user
-
No changes after Preview
- Execute a normal run; preview doesn’t persist writes
-
Proxy/Network issues
- Supply
--proxy http://user:pass@host:portin extra parameters for cURL if required by your network
- Supply
¶ Recommended Settings
-
Number of retries on connection error:
5 -
Extra cURL params: leave blank unless you need proxy/timeout; examples:
--proxy http://proxy:8080--max-time 120
