---
title: "Work Order Status Bulk Update"
slug: "work-order-table-statues-field-update-function"
updated: 2025-09-30T19:01:21Z
published: 2025-09-30T19:01:21Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Work Order Status Bulk Update

*This function can bulk update the status field in multiple work orders.*

<section class="infoBox">
          <div class="title">Who can use this feature
</div>
          <div class="content">
              <p>As of r338, Functions is in Production Early Access. To request access, contact your Customer Success manager. 
              </p>
</div></section>

**Read more in the Community thread [here](https://community.tulip.co/t/functions-production-release-available-for-early-access/15658).**


## Introduction
Functions allow your team to build shared or standardized logic once, and then reuse in multiple apps. In this example we are showcasing functions which can bulk update the status field in multiple work orders. 

### Function Flow
The function's flow is shown below:
![image](https://tulip.widen.net/content/9yyhq4vezy){height="" width=""}

### Walkthrough
Functions are triggered by a trigger in an application. In the function, you can define inputs that need to be provided by the trigger that calls the function.

In this specific function, we require two inputs.
![image](https://tulip.widen.net/content/v68aartgbk){height="200" width=""}

The first input is a variable list of Work Order IDs, and the second is a Status variable.

These two variables are provided to the function call by the trigger.
![Screenshot 2025-07-17 at 15.05.02.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-07-17%20at%2015.05.02.png){height="" width=""}

The function uses these inputs to execute.

First, the function is called by a trigger. After the function call, a looping action takes place. Here, the input is the previously mentioned Work Order IDs variable list.

![Screenshot 2025-07-17 at 15.07.18.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-07-17%20at%2015.07.18.png){height="" width=""}

Next, the function gets the first record from the Work Order table based on the ID from the looping action.

![Screenshot 2025-07-17 at 15.10.04.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-07-17%20at%2015.10.04.png){height="" width=""}

In the next action, the function will update the status field of the selected record with the value provided in the app under the status variable.

![Screenshot 2025-07-17 at 15.13.14.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-07-17%20at%2015.13.14.png){height="" width=""}

This will repeat until the Work Order IDs variable list is empty.

### Modifying the function
In the function, you can modify almost everything to fit your process. This specific function uses the Work Order table, but if you would like to use a different table, you can do so by modifying the relevant actions to reference your table instead of the Work Order table. Additionally, if you want to update more fields or different fields, you can do so by changing or duplicating the Update Order Status action.

## Further Reading
*If you would like to get to know more functions, check out these other documents to extend your knowledge*


* [Function Overview Article](https://support.tulip.co/docs/functions)
* [Work Order Table Fields Update Function ](https://support.tulip.co/docs/work-order-table-fields-update-function)
* [Create ID with sequential numbers](https://support.tulip.co/docs/create-id-with-sequential-numbers)