Integration of “BAS” with "Bitrix24"  - universal exchange between "Bitrix24" and “BAS” objects.

The solution can work on the cloud and box "Bitrix24". Settings on the side of "Bitrix24" are made in the form of scripts, without changing the "Bitrix24".

How implemented:

• API commands have been added to "BAS". The interaction system is designed so that "Bitrix24" is the active side, and "BAS" is the party sending and receiving information.

• Correspondence of objects (entities) and their fields is configured on the side "BAS".

• The minimum "Bitrix24" tariff is "CPM +". No transfer to the “Company” tariff is required, as for a standard exchange with Bitrix24.
  

To configure the exchange, the following metadata objects are used:

1. Directories "Bitrix24".

2. Metadata structure.

3. Exchange entities with "Bitrix24".

Fig.1. Data for sharing settings.

1. "Directories Bitrix24" (+ Directory "Values of directories Bitrix24").

It is possible to adjust the correspondence of the reference type values (directory, enumeration, ...) to the values in "Bitrix24". This is done for those cases when the string representation of the values of the directory (enumeration) does not (always) correspond to its analog in "Bitrix24" (Figure 2).

The exchange of values for the details is carried out in the correspondence directories of the "Bitrix24" and "BAS" objects, without changing the program code.

List of directories for exchange:

• Counterparties;
• Contact persons;
• Warehouses;
• Warehouse balances;
• Products;
• Business Process.

Fig.2. Configure the correspondence of the reference type values (directory, enumeration, ...) to the values in "Bitrix24".

Correspondence of the values of the "Bitrix24" directories- Setting the correspondence of reference values to the values in "Bitrix24".

Fig.3. Configuring the correspondence of reference values to the values in "Bitrix24".

2. Metadata structure is a representation of the metadata involved in the exchange with "Bitrix24" as a reference (Figure 4).

Fig.4. Metadata structure.

3. Setting correspondence to "Bitrix24" entities or related elements in "1C:Підприємство".

This exchange scheme assumes the ability to customize (without changes to the code or other configuration changes) the existing set of entity exchange fields, provided that the "BAS data types used in the basic delivery are used (for example, simple types (string, date, number, Boolean) ). This is done by creating (if necessary) the entry in the directory structure of the metadata structure and appendices, indicating the corresponding field of the "Bitrix24" entity (the entity element of the Essence Exchange with "BAS"). Similarly for related objects: add the Element of the Entity entity with "BAS" and set up a link to the associated object (Fig. 5).

Similarly, if you need to exclude some fields from the exchange, you can without resorting to changes in the code. It's enough just to mark the element of the Essence exchange with "BAS".

In the exchange set, there are also programmable fields that can not be determined by simply matching the details of the directory/document or the associated object. In such cases, the code will not work without changes in the code. As an example of such a field, you can enter the parameter Annual turnover. There is no such counterpart in the directory, but there is a display of this indicator on the form of the element, and the data itself is taken from the object for a certain period from the corresponding register. Obviously, for such fields only one-way exchange is provided (ie, only the unloading from "BAS" to "Bitrix24")

But, as practice has shown, there are not many such fields, and in most cases there is a one-to-one relationship (one requisite "BAS" corresponds to the field of "Bitrix24").

Fig.5. The essence of metadata.

For convenience of information perception, one-type fields from linked objects can be linked to a nested group (Figure 6).

Fig. 6. An example of related fields of the same type with objects placed in a nested group (contact information fields).

But this is allowed only for related objects. Exchange fields with a one-to-one link must necessarily be in the root group of the entity!

For linked objects, it is possible to configure a different selection for uploading to "Bitrix24" and downloading from it. When unloading into "Bitrix24", for example, contact information with the type "Phone" can be downloaded, and the same field will be downloaded not only with the type Phone, but also with the type "Worker" or "counterparty phone" or "counterparty phone from "Bitrix24"". For unloading, you can specify "not strict" selection, and for recording in "BAS", you must specify the selection as precisely and specifically as possible. Otherwise, when writing data to the register, an error may occur and the downloaded data from "Bitrix24" to "BAS" will not be recorded.

There is a link not only to the metadata requisite with the corresponding field of the "Bitrix24" entity, but also to the categories, and the associated reference book and data register, with the possibility of setting the selection (Fig. 7).

Fig.7. The association of metadata with the category, the associated reference book and the information register, with the possibility of setting the selection.

Registers of information.

"Bitrix24" - Storage of "Bitrix24" object identifier in "BAS".

Fig. 8. Storing an object identifier.

Bitrix24 download protocol - Exchange error correction. If necessary, you can record, including successful operations.

Fig.9. Fixing Exchange Errors.

The exchange of values for the details is carried out in the correspondence directories of the "Bitrix24" and "BAS" objects, without changing the program code.

Developer: NCT Company

www.nct.ua
info@nct.ua

Variants of the proposal: