Skip to content

Add Odoo domain filter documentation #2989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Odoo domain filter documentation #2989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
44 changes: 38 additions & 6 deletions docs/integrations/builtin/app-nodes/n8n-nodes-base.odoo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,12 +26,6 @@ Refer to [Odoo credentials](/integrations/builtin/credentials/odoo.md) for guida
* Get a contact
* Get all contacts
* Update a contact
* Custom Resource
* Create a new item
* Delete an item
* Get an item
* Get all items
* Update an item
* Note
* Create a new note
* Delete a note
Expand All @@ -44,6 +38,44 @@ Refer to [Odoo credentials](/integrations/builtin/credentials/odoo.md) for guida
* Get an opportunity
* Get all opportunities
* Update an opportunity
* Custom Resource
* Create a new item
* Delete an item
* Get an item
* Get all items
* Update an item

## Custom Resources

When calling a custom resource you are able to call any model in Odoo. The call is transformed into a JSON RPC call on the Odoo side of things. This is helpful to keep in mind when building the filters.


### Adding a filter

Click **Add condition** after selecting **Custom Resource** from the **Resource** dropdown. These filters work well for discrete values. If there are values in your Odoo instance that are falsey or truthy then it might be better
to use a **Domain filter**.

### Using domain filters

The **Domain Filter** field is only available for **Custom Resource**. It takes a JSON object and passes it to Odoo's JSON RPC. Odoo converts this into a Python Tuple to filter the model on upon execution. Below is a table for some Odoo domains and how they would be entered in the string field of **Domain Filter** in the Odoo node on n8n.


| Odoo Domain Filter | n8n Odoo Domain Filter String |
| -------------------- | ------------------------------------------------ |
| `[("intended_use", "=", False)]` | `[["intended_use", "=", false]]` |
| `["&", ("detailed_type", "=", "product"), "&", ("type", "=", "product"), ("reduced_template_price", "!=", False)]` | `["&", ["detailed_type", "=", "product"], "&", ["type", "=", "product"], ["reduced_template_price", "!=", false]]` |

You can "convert" a tuple to a JSON object by copying the Python Tuple and running it with a simple Python script:

```python
import json

tuple = [("intended_use", "=", False)]
json.dumps(tuple)

# outputs: [["intended_use", "=", false]]
```


## Templates and examples

Expand Down