...
This step is used to return OpenERP object data using the XMLRPC interface. It makes use of the standard OpenERP 'read' function and returns rows that satisfies satisfy the specified filter.
Since: PDI version 4.3.0-M1, September 9th 2011, PDI-6661
Options
Option | Description |
|---|---|
Step Name | Name of the step; the name has to be unique in a single transformation |
Connection | The OpenERP database connection from which to read data from |
Model Name | The model/object to read data from |
Read Batch Size | The maximum amount of rows to return with each call. |
Filter | Specifies search criteria. If no filter is specified, all records are returned |
Field to retrieve | List of fields to read |
...
Option | Description |
|---|---|
Operator | Supports AND, OR, NOT. AND is the default option if no operator is specified. If you need to use OR, please read the OpenERP documentation of on filtering. |
Field | Model/Object field to filter on |
Comparator | Supports =, !=, >, >=, <, <=, like, ilike, is null, is not null, in, not in, child_of, parent_left, parent_right |
Value | Constant value that will be compared to the model field |
...
To Filter on res.partner where the partner is either a customer or OR a supplier, you would do:
Model fields
All model fields are returned by the step including related, many2many, many2one, function, selection fields etc.
...
many2one fields return the ID and Name of the parent object. The postfix "_id" and "_name" is added to the original field name.
For example: The field country returns two fields: 1. country_id (for the ID number) and 2. country_name (for the country name). The same will go for salesman (user_id_id and user_id_name).
...