Odoo Reader
Note
This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.
Odoo is an open-source suite of business applications that covers a wide range of business functions, including CRM, accounting, inventory, sales, project management, eCommerce, and more. It offers a modular approach, allowing businesses to install only the apps they need, and is recognized for its flexibility and ease of customization.
The Odoo Reader connects with the Odoo platform and reads supported objects.
Feature summary
Feature | Supported? | Notes | |
---|---|---|---|
Objects | Standard objects | ✓ | |
Custom objects | ✓ | ||
Authentication | Basic authentication | ✓ | Username and password |
OAuth authentication | Manual configuration based | ||
Custom authentication methods | Not all methods may be supported | ||
Operations | Automated mode | ✓ | |
Initial load | ✓ | ||
Pull-based incremental load | ✓ | ||
Push-based incremental load | |||
Automated pipeline | |||
Governance | Connection profile | ||
Sherlock AI | |||
Sentinel AI | |||
Schema handling | Initial schema creation | ✓ | Works with supported targets |
Schema evolution | |||
Setup | Wizard template | ||
Flow Designer | ✓ | ||
Striim TQL | ✓ | ||
Runtime | Resilience/recovery | ✓ | |
Parallel execution | |||
Metrics | ✓ | Standard metrics |
Supported authentication method
The Odoo Reader supports basic authentication using an API token. In Odoo you can generate an API token which functions as a key to access the system.
Supported objects
The following are the supported objects for reading from Odoo:
FieldReferences
Odoo Reader properties
Property | Type | Default value | Notes |
---|---|---|---|
URL | String | The base URL of the Odoo site you're connecting to. For example, http://my.odoo.com/. | |
Username | String | The Odoo user account used to authenticate. Together with the API token, this field is used to authenticate against the Odoo server. | |
API token | Password | The API token used to authenticate the user. | |
Check permissions | Boolean | True | Whether to use Odoo user's permissions to determine which tables and views to list. Each user in Odoo has different permissions to access, read, or modify models. When this property is true (the default), the model permissions are examined so that modifiable models are classified as tables, read-only models are classified as views, and inaccessible models are not listed. |
Connection pool size | Integer | 20 | Specifies the maximum number of active connections. |
Exclude tables | String | A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. | |
Incremental load marker | String | The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval. Specify the name of the column that contains the start position value. This column must meet the following criteria:
| |
Migrate schema | Boolean | False | Only available in Initial Load or Automated mode. Set to |
Mode | Select list:
| Automated | Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load. |
Polling interval | Integer | 5m | Specifies an interval as an integer followed by a unit. Supported units are days ( |
Refresh token | Password | An OAuth 2.0 refresh token.Use the value generated while creating the token. | |
Start Position | String | %=-1 | Value of the incremental load marker that defines the initial reading position. |
Tables | String | A semicolon-delimited (;) list of objects to read from the source. Supports the | |
Thread pool count | Integer | 10 | The number of parallel running threads. The default value of zero specifies single-threaded operation. When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice. |