Exchange using standard 1C functionality
Posted: Sat Dec 21, 2024 3:41 am
An example of displaying the standard exchange functionality in the interface
If the first method does not suit you, then it is worth studying what comes "out of the box" in 1C of your configuration. The structure of the catalog on the site will be identical to the structure of the nomenclature in 1C (at least we have not yet seen the ability to customize the exchange tree in the standard functionality).
Unloading changes does not take into account the hierarchy accurate mobile phone number list and unloads changes to the root of the directory, and therefore is incorrect (one of the typical shortcomings of many configurations). From the documents, only the orders themselves with the composition are unloaded. Without shipments, payments and other related information. As a rule, there is no unloading of counterparties and user directories.
The exchange functionality "out of the box" is much more modest than the special 1C-Bitrix module. In this case, experienced 1C specialists come to the rescue and refine this functionality.
3. Exchange via web services
Example of a web service in 1C
You can read more about what web services are on the page.
In short and simple: the site sends a request in a certain format to 1C, 1C responds with the necessary information in a given format - request-response mode (usually a post-request and response in json or xml).
This option will require the development of the web services themselves on the 1C side and the development of exchange software on the site side. As a rule, this requires a lot of time and direct communication between technical specialists.
In this way, it is possible to implement any, even the most complex and atypical exchange, with absolutely any data that is on the site or in 1C.
This approach is very expensive to develop and should be used when it is necessary to create something truly exclusive, unique, and atypical.
When choosing this method, it should be taken into account that exchange via web services can be used either completely independently or in combination with the first and second options.
It is important to understand that in all the above cases you need a 1C specialist with varying degrees of involvement depending on the integration method. But in any case, the higher his qualifications and experience in working with exchanges, the faster and better the result will be and the more nerves will be saved for the entire project team and for you, as the customer.
The decision on which of the above options to choose depends on the tasks, capabilities and abilities of 1C specialists. But you should understand that synchronization almost never happens with a wave of a magic wand (in our experience, this is 1 in 10 cases), and you need to be ready for modifications on the 1C side, and even rebuild some of the usual work processes. However, the result, the automation, the man-made magic that was so meticulously created by joint efforts, provides indescribable convenience, as well as significant time savings and a reduction in manual labor.
If the first method does not suit you, then it is worth studying what comes "out of the box" in 1C of your configuration. The structure of the catalog on the site will be identical to the structure of the nomenclature in 1C (at least we have not yet seen the ability to customize the exchange tree in the standard functionality).
Unloading changes does not take into account the hierarchy accurate mobile phone number list and unloads changes to the root of the directory, and therefore is incorrect (one of the typical shortcomings of many configurations). From the documents, only the orders themselves with the composition are unloaded. Without shipments, payments and other related information. As a rule, there is no unloading of counterparties and user directories.
The exchange functionality "out of the box" is much more modest than the special 1C-Bitrix module. In this case, experienced 1C specialists come to the rescue and refine this functionality.
3. Exchange via web services
Example of a web service in 1C
You can read more about what web services are on the page.
In short and simple: the site sends a request in a certain format to 1C, 1C responds with the necessary information in a given format - request-response mode (usually a post-request and response in json or xml).
This option will require the development of the web services themselves on the 1C side and the development of exchange software on the site side. As a rule, this requires a lot of time and direct communication between technical specialists.
In this way, it is possible to implement any, even the most complex and atypical exchange, with absolutely any data that is on the site or in 1C.
This approach is very expensive to develop and should be used when it is necessary to create something truly exclusive, unique, and atypical.
When choosing this method, it should be taken into account that exchange via web services can be used either completely independently or in combination with the first and second options.
It is important to understand that in all the above cases you need a 1C specialist with varying degrees of involvement depending on the integration method. But in any case, the higher his qualifications and experience in working with exchanges, the faster and better the result will be and the more nerves will be saved for the entire project team and for you, as the customer.
The decision on which of the above options to choose depends on the tasks, capabilities and abilities of 1C specialists. But you should understand that synchronization almost never happens with a wave of a magic wand (in our experience, this is 1 in 10 cases), and you need to be ready for modifications on the 1C side, and even rebuild some of the usual work processes. However, the result, the automation, the man-made magic that was so meticulously created by joint efforts, provides indescribable convenience, as well as significant time savings and a reduction in manual labor.