Quick Configuration of Integration Flow via Import

Operation Entry

Create a new data integration flow -> Template import -> Select connector -> Download template -> Upload Excel file

picture coming soon:

picture coming soon:

Template Instructions

picture coming soon:

Each sheet maintains the “field mapping” configuration for one integration flow. Multiple integration flows can be imported at once. The sheet name will be used as the integration flow name.

[1] Source System
Indicates the direction of the integration flow. If the flow is CRM -> Third-party, enter “CRM”; for the reverse direction, enter “Third-party”.

[2] CRM Object Information
Specify the CRM object and fields to be integrated. The object’s ApiName and field ApiName are mandatory.

To integrate Sub-objects, first fill in the Primary Object fields, then proceed to the Sub-object fields below. Note that the Primary Object must always be specified.

[3] Third-party Object Information
Required fields: Object Name, Object Code, Field Name, Field Code, Field Type, and Required Flag. Note: “Object Code” refers to the third-party object code, not the intermediate object code.

For fields of type Single Select, Multi-Select, Lookup Relationship, or Lookup Relationship (Multi-Select), extension information is also required.

For Sub-object integration, follow the same rule: fill in the Primary Object fields first, then the Sub-object fields.

System Execution Logic:
The system first verifies whether the third-party object exists under the selected connector based on the “Object Code”:

• If it doesn’t exist, the system will create the object and fields.
• If it exists, the system will neither create nor update the object. It will then check whether the field exists based on the “Field Code”. If the field doesn’t exist, it will be created; if it exists, no action will be taken.
• For detail objects, they are automatically created as first-level Sub-objects of the Primary Object.

Extension Information Examples:
- Single Select/Multi-Select:
json [{"value":"Option1Code","label":"Option1Name"},{"value":"Option2Code","label":"Option2Name"},{"value":"Option3Code","label":"Option3Name"}]
- Lookup Relationship/Lookup Relationship (Multi-Select): Enter the intermediate object code of the related object.

[4] Use separate sheets for different integration flow configurations. Sheet names must be unique.

Integration Flow Generation Logic

• If the third-party object doesn’t exist under the connector, it will be automatically created along with its fields.
• If the third-party object already exists, missing fields will be added.
• The template generates: Integration Flow Name, Source System, Source Object, Target System, and Target Object.

Default Actions:
- For Third-party -> CRM:
- Trigger: Query (every 6 minutes from 00:00 to 23:59 daily).
- Execution: Create, Edit, Invalidate.
- For CRM -> Third-party:
- Execution: Create, Edit.

Default Status: Disabled.

Validation Notes:
- If an integration flow with identical source and target objects already exists, no new flow will be generated or updated. It’s recommended to delete the existing flow before re-importing.
- No value mapping will be performed for Single Select or other enumerated types.

After import, adjust the object fields and integration flow configurations as needed.