Under the docking object of the connector, when maintaining the fields that need to be docked, the information of the related fields can be obtained in the following ways:

In Kingdee Cloud Starry Sky (including early K3 Cloud version) web api query interface

Find the corresponding business document in the left column, click

Select Save from the action list on the upper right

Click the field description to view the specific field name and corresponding apiname, click the online test WebAPI at the top, fill in the account information in the pop-up window, click the verification interface, select Save in the operation list, and the corresponding data format will be displayed in the test data box (for easy viewing You can copy the data format and place it in the web version of the json verification tool or notepad+ tool to view), and check the field apiname by field name against the field description.

Take the sales order as an example, split the ERP sales order into master-slave intermediate objects, and illustrate the master object and slave object fields respectively. The left side is ERP view, and the right side is the online test of display effect of data formatting in Web which is taken out from WebAPI save interface list:

Example: Main Object Field Code / Save Interface Field Code

Notes: FSaleOrderFinance needs to be added here, because the financial information is the sub-document header;

Example: Sub-object Field Code/ Save Interface Field Code

Special Notes: There is no need to add the prefix FSaleOrderEntry here, because when the ERP object splits the intermediate object, the detailed code has been filled with SAL_SaleOrder.FSaleOrderEntry, and the program already has processing logic;

View Interface Field Code

On the Kingdee Cloud Starry Sky (including the early K3 Cloud version) web api query interface, find the corresponding business document in the left column, click it, select Save from the operation list on the upper right, and check the specific field name and corresponding apiname in the fifth field description. Click the online test WebAPI at the top, fill in the account information in the pop-up window, click the verification interface, select View in the operation list, add the document number in the Number field in the test data box, and click the interface verification in the menu bar to view the order view interface of the document number The specific fields returned (you can copy the data format and place it in the web version json verification tool or notepad+ tool for easy viewing), and check the field apiname through the field name according to the field description.

Taking the sales order as an example, split the ERP sales order into master-slave intermediate objects, and illustrate the master object and slave object fields respectively. The left side is ERP view, and the right side is the online test WebAPI view interface. The display effect of the webpage after formatting:

Example: Main Object Field Field Code Viewing

Special Notes: Check the interface and pay special attention to the fact that the apiname of the field returned by the actual interface is different from that of the field description. For example, the field description of the document number field (apiname: FBillNo) has an F prefix, but the actual return does not. The actual return of the interface shall prevail!

Instructions for filling in the return field of the language structure view interface:

Example: Sub-object Interface Field Code Viewing

Special Notes: There is no need to add the SaleOrderEntry prefix here;

Save the interface field code: the same as the above field code writing rules, do not go into details;

Is it required: according to the actual choice;

Field Type: according to actual selection;

Each ERP intermediate object must have a primary key field, which is used to represent the unique identifier of the data in the integration platform. At present, some primary key fields are set to ERP codes such as customer and product, some are set to ERP internal code id#document number such as the main object of sales order, and some are set to ERP internal code id such as batch and serial number. The primary key field of the ERP preset object cannot be changed easily, please be careful if you need to change it

In data maintenance, the third-party object data ID is the data represented by the primary key field

Certain fields in an object need to be associated with the object data of another object, which can be configured by looking up associated fields. For example, the account field in the sales order needs to be associated with customer object data, then set this field to look up the association - the associated object is account

In the field mapping of the integration flow, the lookup associated field can only be mapped with the lookup associated field or set to a fixed value

When an ERP object is split into an intermediate object of a master-slave relationship, the slave object needs to set a virtual master-slave field for master-slave association. The field encoding of the virtual master-slave field is usually set to [fake_master_detail], and the associated object is set to the master object that needs to be associated. For example, a sales order is split into an intermediate object of a master-slave relationship, and the virtual master-slave field is set in the order details of the slave object as follows

The radio field is not much different from the radio that is usually used in other places. The radio field needs to configure the option code and option name, as follows

In the field mapping of the integration flow, the radio field needs to map the options

When there are many options, if the option names on both sides are basically the same, you can use the "sub-option name automatic mapping" operation to quickly map

A fixed value means that the field is set to a fixed value. After the configuration is set to a fixed value, all data that is successfully synchronized will have the fixed value set in the field mapping. For example, the document type (code) field is set to a fixed value -- XSDD01_SYS, then the data that is successfully synchronized after setting, the value of the document type (code) field is XSDD01_SYS

The fixed value is configured in the field mapping of the integration flow, click Insert Value and select to enter a fixed value, then you can set the fixed value

The default value is set to the default value if the mapped field is not filled in or the value is not obtained. For example, the field mapping between "name" and "job name" in the figure below, the default value is set to sk001, assuming that the name field of a piece of data is not filled, after the synchronization is successful, the value of the version number field of the corresponding data in the target system is sk001

If the CRM department wants to connect with the ERP department, it needs to create a department field for mapping

First establish the mapping of departmental data. Department field data mapping is under the corresponding connector - "system field" management

In departmental data mapping, CRM departments can be mapped with ERP departments by creating or importing

The CRM basic data ID and CRM basic data name can be obtained by referring to the following figure

Among them, fill in the code of the ERP department for the ERP basic data ID, and fill in the name of the ERP department for the name of the ERP basic data

Later, in the field mapping of the integration flow, you can map the department field

1. There are two docking methods for the personnel field, one is the salesperson code, and the other is the employee ID. Usually, the salesperson code is selected. If the employee ID needs to be displayed in data maintenance, use the employee ID to connect

2. First, bind personnel in Data Synchronization Settings - Account Binding. K3C recommends using [Synchronize ERP staff account] to synchronize ERP staff. When synchronizing ERP staff, it will automatically match the CRM staff account according to the mobile phone number of the ERP staff. If it fails to match, click [Edit] in the operation column to manually bind the CRM employee account

3. After the personnel are bound, map the personnel field in the integration flow, as shown in the figure below

4. If the same person has different salesperson codes in different departments of K3C and needs to connect with salespersons, you need to add a field with the field code [ERP_Dept] in the ERP intermediate object and configure the field mapping

First add a field, the field code is [ERP_Dept], the field name is arbitrary, the field type is single choice, and the option code and option name are filled with the department name

Add the mapping of this field in the integration flow, and create a radio field in CRM to map with it