Container for [Data Object Name]
The Data Object Container in Workmaster acts as the parent container for form inputs and connects them to a backend Data Object. It enables forms to either create a new record or update an existing one based on the presence of an ID in the submitted data.
What It Does
When placed on the page and the form is submitted:
Inserts a new record if no existing record with the same ID is found.
Updates an existing record if a matching ID already exists in the linked Data Object.
This makes it ideal for dynamic form-based workflows.
Key Considerations
Make sure each widget’s Element ID matches the respective Data Model field.
You must know the exact field names in the Data Object to bind accurately. You can check the field names of relevant Data Objects under the Data Tab of Workmaster.
Always verify that the Submit Button triggers the correct action (
Save Page Data
).
Step-by-Step Guide to Use the Data Object Container
Step 1: Add the Widget
Open the Widget Panel on the left, go to the Layouts section, and click & drop the Data Object Container onto your page.

Step 2: Place Input Fields
Inside the Data Object Container, add your input widgets such as text fields, date pickers, or dropdowns. These fields will represent the attributes of your Data Model — for example, fields like employeeName
, startDate
, or leaveReason
.

Step 3: Bind Fields via Element IDs
Bind each input by setting its Element ID. The Element ID must match the corresponding field in the Data Model.
Example:
taskOwner
taskOwner
startDate
startDate
leaveReason
leaveReason


Step 4: Submit the Form
To make the form work, add a Submit Button to your page and assign it the Save Page Data
action.

On submission:
If an ID exists in the container → the record is updated.
If not → a new record is created in the connected Data Model.
Step 5: Preview & Test
Preview the form in the editor to test your setup. Try creating a new record and then editing an existing one by pre-populating the container with its ID. Ensure that all bound fields are saving or updating correctly based on your configuration.
Last updated