Two-way integration Odoo and 1C8.x
use any Odoo configuration and any 1C configuration
The application provides the functionality of setting up a two-way data exchange and implements
the data exchange itself between 1C and Odoo databases of any (!) Configurations.
As Odoo can be with any composition of models \ tables (including unique ones), so 1C can be absolute in any configuration (including completely self-written).
Export data from Odoo to 1C
Import data from 1C to Odoo
What are the Rules of "Integration" or "Matching" or "Exchange"?
A small remark
The base 1C has its own objects (Directories, Documents, Registers, ...) and their fields.
The Odoo database has its own models (sets of tables) and their fields.
Before exporting data from one system into another, you need to specify FROM which tables and fields of one system INTO which tables and fields of another system your need to export your data.
This process is called setup: "Matching Objects and Fields" or "Conversion Rules" (in 1C terminology).
This "matching" is implemented either "hard" in the program code, or stored in separate "integration rules" files or in database.
Integration files in which the "Rules for matching objects and their fields" are stored, can be edited either manually or through the Integration Designer.
Of course, the Integration Designer is the most convenient way to configure the "Integration Rules".
This Application implements the configuration of the exchange through the Constructor called "1C: Conversion 2.1".
The Designer "1C: Conversion" is free(!), flexible, open, standard (ie, "native" for 1C), run-in for years product, massively used and recommended by all, with good documentation, reputation, correct architecture, a lot of examples, a large community.
Powerful designer of "Integration rules"
Easy change the Integration rules without changing the program code
The world is boiling up and if your system does not evolve in accordance with the challenges of time, then it will inevitably be waited for by a stop and archive peace.
But if your system (1C and \ or Odoo) is changing very actively (often new tables, fields are added, current tables are changed, ...)
then you will need to reconfigure the "Rules for matching fields and tables" relatively often.
If the "Rules for matching fields and tables" are embedded in the code("hardcode"), then you will have to overpay for the services of developers.
This Application will allow you on your own, quickly and without changing the code - to change the "Rules for matching objects and fields" in "Designer of Integration rules".
Matching Odoo and 1C Sale Order fields in Designer "1C:Conversion"
Odoo crm lead field kanban_state in 1C Conversion
Odoo crm lead structure in 1C Conversion
Odoo sale order structure in 1C Conversion
This will greatly save you not only your money, but also time.
The quick setup of integration between any, even self-written, Odoo and 1C configurations is a huge plus, but we believe that it is not the most important one. The main advantage of this functionality is that setting the matching fields and tables (exchange rules) Odoo and 1C can be done quickly, easily, independently (by business analysts or advanced users) without the need to change the code and without contacting the developers(Odoo or 1C developers).
Example adding exchange rule: 1C Contact VAT -> Odoo Contact VAT
The basic idea
...and algorithm of initial setup
1. This Application creates a description of the structure of the Odoo database(tables and fields) and saves it in an xml file.
2. In the 1C database, by processing MD83Exp.epf or MD82Exp.epf, a description of the structure of the 1C configuration is created and stored in the xml file.
3. Files with structures (configurations) 1C and Odoo - are loaded into the "database 1C:Conversion of data 2.1" (see the documentation of 1C:Conversion).
How to setup Odoo and 1C Integration
These first three points are made only one(!) times when you first set up.
4. In the 1C Conversion database - the Rules for converting objects and the Rules for export are created\change.
5. The created "Integration Rules" are saved in the xml-file, which is used to export data.
If you want to change the rules of data exchange, then proceed with paragraphs 4 and 5. When exporting data is converted and marked in what fields they should be loaded. To do this, use the file "Exchange rules". When importing data, there is all the information required to load the data and the file "Exchange Rules" is not required.
In side 1C, native processing "Universal Data Exchange" is used
Flexible and powerful integration
Customization of non-standard and difficult Conversion Rules
You can set the most complex rules for converting values.
You can write your own data conversion algorithms without having to change the Odoo or 1C program code. Therefore, no restart of the systems (Odoo or 1C) is required to apply the new program code. Therefore, you can dynamically change and expand the integration rules without stopping work.
A few examples:
Converting the value of the 1C field into a row of the Odoo table
Convert the Boolean value of the Odoo field into 1C field with type Selection
Search for a row of a table ("Directory") 1C across the field ("Name"), containing a certain value
Convert the Odoo field Link type to 1C field Selection type
try it online and free
Configuration: Accounting for Ukraine 2.0
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.