Odoo ERP Export Field Settings
In addition to its own Odoo ERP specific feature set, the Odoo ERP Integration implements a subset of Common Extended Features.
| Extended Feature | Identifier Field |
| Extended Feature | Default Value, when Empty |
| Extended Feature | Exclude / Dissolve / Promote, when... |
Each Export Field has a source value, and that value can be mapped to several target Odoo table fields. All mappable tables are listed as tabs, starting with naming convention Odoo: <table>.
| Map '<table>' field: |
Select the target field to map to.
|
| Identify '<table>' using '<secondary table>' field: |
Select the target field to map to from the <secondary table>. If the type is [float], you should define that the field contains Numeric value(s) in Source tab. |
| Separator | Separator for multiple results obtained from [One2Many] and [Many2Many] field types. |
| Insert to Odoo | When Odoo does not have an object in its corresponding <table>, a new one is created. If Insert to Odoo is set, that new object will get its value from this field. |
| Update to Odoo | When Odoo has an object in its corresponding <table>, that object is linked to Export. If Update to Odoo is set, that existing object will be updated based on the value in this field. |
| Data Master |
SOLIDWORKS: Export view shows the field value as defined in Source tab. Odoo <table>: Field value is overridden by value of an existing mapped object of this table in Odoo. |
| Import to Model | When Data Master is one of the Odoo tables, the overridden field value can be imported to the model during Export, if the original Source of the field is ATR CustomTools attribute. |