> ## Documentation Index > Fetch the complete documentation index at: https://help.dingtalk.io/llms.txt > Use this file to discover all available pages before exploring further. # Bulk Submission > Learn how to use the bulk submission feature for YiDA workflow forms, including supported capabilities, procedures, use cases, and FAQs. | **Feature** | **Free plan** | **Basic edition** | **Professional edition** | **Dedicated edition** | | ------------------------ | ------------- | ----------------- | ------------------------ | --------------------- | | Bulk workflow submission | Not supported | Supported | Supported | Supported | ## 1. What Is Bulk Submission YiDA workflow forms let app admins submit workflows in bulk by uploading an Excel file from the app backend. Bulk submission currently supports the following capabilities: (1) Submit workflows on behalf of others. If a column in the Excel file contains initiator information, you can designate that column as the workflow initiator. (2) Submit workflows using the YiDA platform public account. For example, when tracking the resolution of external user complaints, the initiator should be a public account rather than an individual. (3) Dynamically assign workflow handlers based on a specific column in the Excel file. For example, in an Excel file that tracks external customer follow-ups, one column may contain the follow-up owner. You can designate that column as the workflow handler at submission time. (4) Delete bulk-submitted data by batch. If a bulk submission fails or does not meet expectations, you can delete the data directly by batch. (5) Format specifications for Excel column data. ## 2. Bulk Submission Use Case **Scenario:** A department wants to reward outstanding employees from the past quarter. Each outstanding employee's manager writes a "nomination statement". Once the manager submits the nomination, the employee receives a message notification to claim the gift. ### 2.1 Procedure #### 2.1.1 Configure the Fields to Fill in on the Workflow Form Workflow form editing page #### 2.1.2 Configure the Workflow so That After Submission, the Recipient's Manager Becomes the First Approver and Writes the Nomination Statement Set the approver #### 2.1.4 Select Excel Bulk Submission The Excel file content is shown below: Excel bulk submission Bulk submission from Data Management **Note: The workflow bulk initiator can be customized** Choose one of the following three types as the data initiator: ① YiDA platform ② The user currently importing the Excel file ③ The user selected in the form's user search box (if multiple users are selected, the first user is used by default) (**If you choose the user search box value as the initiator but the member component value in the form is empty, submission will fail.**) The image shows the "Applicant" set as the user search box component on the form #### 2.1.5 View Bulk Submission Results For records with errors, click to view the failed records directly (successfully imported records are not shown) #### 2.1.6 For Failed Records, You Can Delete the Entire Batch Delete this batch of data The example above demonstrates a failed import to illustrate the bulk import feature. The failure was caused by an incorrect user ID format. Below is an example of a successful import: Once the format is corrected, the import succeeds: **Note**: Member component format: If importing by employee ID, use the format `**Name1(EmployeeID1), Name2(EmployeeID2)**`. The parentheses must be half-width English characters. If importing by employee userId, use the format `**Name1[EmployeeUserID1], Name2[EmployeeUserID2]**`. The brackets must be half-width English characters. ## 3. FAQs When bulk submission fails, check the following: (1) Whether the app is published. Bulk submission works only after the app is published. (2) Whether the initiator is customized as the member component on the form. If so, verify that the user search box has a value and that the format is correct. (3) A maximum of 1,000 records can be imported at a time, and the file size must not exceed 20 MB. (4) Only `*.xls` and `*.xlsx` files are supported. (5) Make sure the header row of the sheet you want to import contains no empty cells. Otherwise, the data on that sheet will not be imported. (6) Bulk-imported data does not support filtering conditions based on "built-in variables". (7) Imported files do not support Excel formula calculations such as `SUM` or `=H2*J2`. (8) Imported images and attachments are re-uploaded to storage and consume attachment capacity. When the workflow approver is set to the initiator themselves and the imported data uses \[YiDA platform] as the initiator, the workflow approval node displays \[YiDA platform] as the approver, and the approval cannot be performed manually. In this case, use the following open API to perform the approval. * Endpoint: /yida\_vpc/process/executePlatformTask.json * Parameters | **Parameter** | **Description** | **Required** | **Example** | **Notes** | | -------------------- | -------------------------------------------------- | ------------ | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | appType | App ID | Yes | APP\_PBKT0MFBEBTDO8T7SLVP |
| | systemToken | App secret | Yes | hexxyyddd | Obtain from App Data. | | userId | DingTalk userId | Yes | yida\_pub\_account | Hardcode as yida\_pub\_account | | language | Language | No | zh\_CN | Available values: zh\_CN / en\_US
Default: zh\_CN | | procInstId | Workflow instance ID | Yes | f30233fb-72e1-4af4-8cb8-c7e0ea9ee530 |
| | outResult | Approval result | Yes | • agree
• disagree |
| | formDataJson | Updated form data | No |
| Reference: Appendix 1 — format for saving or updating form data.
Components included in the parameter are updated; components not included remain unchanged.
Table detail values can only be updated as a whole; you cannot update the value of a single component within a detail. | | remark | Approval comment | Yes | Confirmed and approved |
| | noExecuteExpressions | Whether to skip validation and association actions | No | y | When the task node has validation rules or association actions bound:
y -> Skip validation rules and association actions
n -> Execute validation rules and association actions
If omitted, defaults to n, meaning validation rules and association actions will be executed. | ## 4. Data Import Format for Excel Components As shown in the figure: