Build a Bulk Update Module

This guide walks you through building a UI module that lets Creators upload a CSV file and bulk-update records in an existing Data Model. From a single button click, the module generates an upload URL, uploads the file, runs the update, and checks job status.

Download the example module bundle to use as a starting point. After importing, replace every placeholder before using the module:

BDO Update works with Data Model records. It does not support module submission records.

Prerequisites

• Creator or Express Administrator access to your workspace.

• A target Data Model containing the records to update.

• A CSV file with the updated values; each row must include the field used as the match key (typically _id).

• Familiarity with the Plug-In, Decisions, and File components.

Module Overview

Organize the module into three field groups: for initialization logic, for the Creator-facing UI, and for the backend Plug-In component sequence.

The example Property IDs in this guide use a plugin prefix (for example, pluginExport) for clarity. The platform default for Plug-In components is plug — see Property ID Naming Conventions.

How to read settings tables

The tables below describe each configurable option as it shows in the platform. Values are formatted as follows: inline code — a value to type exactly as shown | Bold — a value selected from a drop-down, radio button, tab, or choice chip | ON/OFF — toggle state | ✓ — checkbox checked | ☐ — checkbox unchecked

Set Up the Field Groups

Create three field groups in the module to keep components organized.

Create the Supporting Fields

Add the following fields to fgConfig. These fields carry data between components throughout the upload and update sequence.

Configure initOnload

The initOnload Initializer component fires when the module first loads and serves as the module's entry point. It has no outputs and no connections to other components.

1. Add an Initializer component to fgOnLoad.

2. Configure the following settings:

   Setting	Value
   Property ID	initOnload
   Trigger Type	New Submission

Configure fileUpload

The fileUpload File component captures the CSV the Creator selects. After a file is chosen, it triggers the ruleFileUpload Decisions component to enable the update button.

1. Add a File component to fgUI.

2. Configure the following settings:

   Setting	Value
   Property ID	fileUpload
   Label	Upload File
   Accepted File Types	.csv

3. Under Triggers, set the Post Upload drop-down to ruleFileUpload.

Configure ruleFileUpload

The ruleFileUpload Decisions component checks whether a file has been selected and enables the btnBulkUpdate Button component when is present. It is triggered by the fileUpload File component after each file selection.

1. Add a Decisions component to fgUI after fileUpload.

2. Configure the following settings:

   Setting	Value
   Property ID	ruleFileUpload
   Trigger Type	Manual

3. Configure the Inputs:

   #	Property ID	Alias	Type
   1	fileUpload	A	Exact

4. Configure the Outputs:

   #	Property ID	Type
   1	btnBulkUpdate	Disabled

5. Add row in the Decision grid:

   fileUpload	btnBulkUpdate_disabled
   (wildcard)	=IF(LEN(A)>0,'no','yes')

Configure btnBulkUpdate

The btnBulkUpdate Button component starts the upload and update sequence. It starts disabled and is enabled by the ruleFileUpload Decisions component a file is selected. On successful validation, it triggers the pluginGenerateUploadLink Plug-In component.

1. Add a Button component to fgUI after ruleFileUpload.

2. Configure the following settings:

   Setting	Value
   Property ID	btnBulkUpdate
   Label	Bulk Update
   Action	Validate
   Initial State	Disabled

3. Under Triggers, set the On Validation Success drop-down to pluginGenerateUploadLink.

Configure btnRefresh

The btnRefresh Button component lets the Creator manually re-check job status. It triggers the pluginGetJobDetails Plug-In component on click, and the ruleCheckStatus Decisions component enables it a job is running. It starts disabled.

1. Add a Button component to fgUI above fileUpload.

2. Configure the following settings:

   Setting	Value
   Property ID	btnRefresh
   Label	Refresh
   Action	Event
   Initial State	Disabled

3. Under Triggers, set the On Click drop-down to pluginGetJobDetails.

Configure initSuccess

The initSuccess Initializer component sets the response field to Success when the update completes without errors.

1. Add an Initializer component to fgConfig.

2. Configure the following settings:

   Setting	Value
   Property ID	initSuccess
   Trigger Type	Manual

3. Configure the Outputs:

   #	Property ID	Type	Value
   1	response	Value	Success

Configure initError

The initError Initializer component sets the response field to Fail when something goes wrong. All Plug-In components in fgConfig reference it as their error handler.

1. Add an Initializer component to fgConfig after initSuccess.

2. Configure the following settings:

   Setting	Value
   Property ID	initError
   Trigger Type	Manual

3. Configure the Outputs:

   #	Property ID	Type	Value
   1	response	Value	Fail

Configure pluginGenerateUploadLink

The pluginGenerateUploadLink Plug-In component gets a pre-signed URL for uploading the file to the Unqork Cloud. It is triggered by the btnBulkUpdate Button component. On success, it triggers the pluginUploadFile Plug-In component.

1. Add a Plug-In component to fgConfig.

2. Configure the following settings:

   Setting	Value
   Property ID	pluginGenerateUploadLink
   Trigger Type	Manual
   Endpoint URL	https://{environment}.unqork.io/fbu/uapi/bulkOperations/uploadLink
   Method	POST

3. No Inputs are required for this endpoint.

4. Configure the Outputs:

   #	Property ID	Value
   1	uploadLink	uploadLink

5. Under Triggers, set the Post Trigger drop-down to pluginUploadFile and the Error Handler drop-down to initError.

Configure pluginUploadFile

The pluginUploadFile Plug-In component posts the file bytes to the pre-signed URL using multipart/form-data. It is triggered by the pluginGenerateUploadLink Plug-In component. On success, it triggers the pluginBulkUpdateRecord Plug-In component. The endpoint URL is built dynamically from the uploadLink field.

1. Add a Plug-In component to fgConfig after pluginGenerateUploadLink.

2. Configure the following settings:

   Setting	Value
   Property ID	pluginUploadFile
   Trigger Type	Manual
   Endpoint URL	/api{{data.uploadLink}}
   Method	POST
   Multipart	ON

3. Configure the Headers:

   #	Property ID	Value
   1	Connect-Type	multipart/form-data

4. Configure the Inputs:

   #	Property ID	Value
   1	file	fileUpload[0]['url']

   Enable Resolve Base64 on the file input so the platform sends the file bytes rather than the base64 string.

5. Configure the Outputs:

   #	Property ID	Value
   1	fileKey	fileKey

6. Under Triggers, set the Post Trigger drop-down to pluginBulkUpdateRecord and the Error Handler drop-down to initError.

Configure pluginBulkUpdateRecord

The pluginBulkUpdateRecord Plug-In component calls the Update endpoint using the fileKey from the upload step. It is triggered by the pluginUploadFile Plug-In component. On success, it triggers the pluginGetJobDetails Plug-In component to begin polling.

1. Add a Plug-In component to fgConfig after pluginUploadFile.

2. Configure the following settings:

   Setting	Value
   Property ID	pluginBulkUpdateRecord
   Trigger Type	Manual
   Endpoint URL	https://{environment}.unqork.io/fbu/uapi/bulkOperations/update
   Method

3. Configure the Inputs:

   #	Property ID	Value
   1	resourceId	'REPLACE_WITH_DATA_MODEL_ID'
   2	fallbackRecordOwner	currentUser['email']
   3	fileFormat	'CSV'
   4	fileLocation	fileKey
   5	name	fileUpload[0]['name']
   6	storeInData	'true'
   7	uniqueKey	'_id' (or the field used to match existing records)

   To insert new records when no match is found, add an eighth input mapping upsert to 'true'. When upsert is false (the default), the operation skips records without a matching key.

4. Configure the Outputs:

   #	Property ID	Value
   1	status	data.status
   2	jobId	id

5. Under Triggers, set the Post Trigger drop-down to pluginGetJobDetails and the Error Handler drop-down to initError.

Configure pluginGetJobDetails

The pluginGetJobDetails Plug-In component checks the status of the update job. It is triggered by the pluginBulkUpdateRecord Plug-In component on success, and by the btnRefresh Button component when the Creator clicks it manually. On completion, it triggers the ruleCheckStatus Decisions component.

1. Add a Plug-In component to fgConfig after pluginBulkUpdateRecord.

2. Configure the following settings:

   Setting	Value
   Property ID	pluginGetJobDetails
   Trigger Type	Manual
   Endpoint URL	https://{environment}.unqork.io/fbu/uapi/bulkOperations/jobs/{{data.jobId}}
   Method

3. Configure the Outputs:

   #	Property ID	Value
   1	status	data.status

4. Under Triggers, set the Post Trigger drop-down to ruleCheckStatus.

All BDO endpoints in this module use the bulkOperations  (camelCase, no hyphen).

Configure ruleCheckStatus

The ruleCheckStatus Decisions component reads the job status written by the pluginGetJobDetails Plug-In component, displays a pop-up message, and enables the btnRefresh Button component while the job is running. When the job reaches completed, it clears and resets fgUI so the Creator can start another update.

1. Add a Decisions component to fgConfig after pluginGetJobDetails.

2. Configure the following settings:

   Setting	Value
   Property ID	ruleCheckStatus
   Trigger Type	Manual

3. Configure the Inputs:

   #	Property ID	Alias	Type
   1	jobId	A	Exact
   2	status		Exact

4. Configure the Outputs:

   #	Property ID	Type
   1	btnRefresh	Disabled
   2	fgUI	Pop Message
   3	fgUI	Multi

5. Add row per job status in the Decision grid:

   Status	btnRefresh_disabled	fgUI_popMessage	fgUI_multi
   created	=IF(LEN(A)>0,'no','yes')	Update started.
   inProgress	=IF(LEN(A)>0,'no','yes')	Update in progress.
   completed	=IF(LEN(A)>0,'no','yes')	Update complete.	clear.reset
   partiallyCompleted	=IF(LEN(A)>0,'no','yes')	Update partially complete.
   canceled	=IF(LEN(A)>0,'no','yes')	Update canceled.
   failed	=IF(LEN(A)>0,'no','yes')	Update failed.

   The formula in the disabled column uses A (the jobId alias). The clear.reset multi-action on completed clears fgUI and resets the form for the next update.

Prepare the CSV

The bulk update CSV differs from a bulk upload CSV. Each row must include the value used as the match key so the platform can locate the record to update. By default, this is the _id column.

The CSV requires the following columns:

A complete CSV looks like this:

_id,firstName,lastName,email
6abeb2b1277a9f5cd3918aca,Todd,Smith,todd.smith@example.com
6abeb2b1277a9f5cd3918acb,Aisha,Patel,aisha.patel@example.com
6abeb2b1277a9f5cd3918acc,Liam,Nguyen,liam.nguyen@example.com

To find the _id values for records you want to update, you can either:

• Export the records using the Build a Bulk Download Module guide, then edit the downloaded file and re-upload it here.

• Open the Explorer tab in the platform, navigate to Utilities > Record Collections > Modules > your module name, and copy the _id from the record you want to update.

Test the Module

1. Open the module in Preview.

2. Select a CSV file formatted as described in Prepare the CSV. The Bulk Update button enables when a file is present.

3. Click Bulk Update.

4. Click Refresh until the pop-up message reads Update complete.

5. Open the submission using the platform's submission inspection method. See Debugger for how to access submission data from Express View.

6. Confirm the jobId and status fields contain the expected values.

7. Navigate to the target Data Model's Record Collection to verify the updated records reflect the values from the CSV.